← previous blocknext block →recent activity
Analyzing
Block #94,250,680
9 transactions · 8 stateful · 2026-08-08 16:18:03 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,250,680 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc9c603ba…3c4a
0x34b655…2a6f
4 touches
1 conflict
0xfd49c1f5…9821
0x34b655…2a6f
4 touches
1 conflict
0x1d3bb43c…1b50
0x1efe02…37d6
2 touches
0 conflicts
0x0494220d…abf6
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0002
0x91855e…ac7e
2 touches
0 conflicts
0x4ee1b275…b43a
0xea1b8e…c5ec
2 touches
0 conflicts
0x57c874be…de5b
0xea1b8e…c5ec
2 touches
0 conflicts
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
1 conflict on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity