← previous blocknext block →recent activity
Analyzing
Block #94,473,439
22 transactions · 16 stateful · 2026-08-09 11:09:00 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,473,439 · 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
6w07w19w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x166b18ee…831d
0x34b655…2a6f
6 touches
3 conflicts
0x7265fa19…9534
0x34b655…2a6f
6 touches
3 conflicts
0x5e8ddd73…4dfb
0x34b655…2a6f
4 touches
1 conflict
0xf565ea1f…4245
0x34b655…2a6f
4 touches
1 conflict
0x1445ffc7…e961
0x34b655…2a6f
4 touches
1 conflict
0x1445ffc7…e962
0x34b655…2a6f
4 touches
1 conflict
0xe128bfa3…4ad4
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity