← previous blocknext block →recent activity
Analyzing
Block #94,742,457
22 transactions · 15 stateful · 2026-08-10 09:42:45 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,742,457 · 22 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
1w02w16w29w310w011w112w113w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54be4d07…5249
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0xa3f095f5…bd87
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0x71392f15…148d
0x065c9d…c394
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
3 conflicts on slot 0x54be4d0749…1a5249
Audit this contract →
← previous block·next block →recent activity