← previous blocknext block →recent activity
Analyzing
Block #94,489,938
20 transactions · 16 stateful · 2026-08-09 12:31:59 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,489,938 · 20 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
8w09w110w213w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xa94bb4af…a8ff
0x968279…9342
6 touches
3 conflicts
0x717ba126…a1e6
0x968279…9342
6 touches
3 conflicts
0x717ba126…a1e7
0x968279…9342
6 touches
3 conflicts
0x717ba126…a1e9
0x968279…9342
6 touches
3 conflicts
0xa94bb4af…a8f8
0x968279…9342
6 touches
3 conflicts
0xa94bb4af…a8f9
0x968279…9342
6 touches
3 conflicts
0xa94bb4af…a8fc
0x968279…9342
6 touches
3 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
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity