← previous blocknext block →recent activity

Analyzing

Block #97,465,945

18 transactions · 16 stateful · 2026-08-19 23:03:35 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,465,945  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0x103de0…bb55

6 touches
3 conflicts

0x11a48d6a…cafb

0x40c49f…2af0

4 touches
1 conflict

0x38c47502…1005

0x34b655…2a6f

4 touches
1 conflict

0x4188ba99…8aa4

0x34b655…2a6f

4 touches
1 conflict

0x94789504…4524

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Perpl

6 conflicts on slot 0x737acb7813…fafce8

← previous block·next block →recent activity