← previous blocknext block →recent activity
Analyzing
Block #94,220,412
10 transactions · 7 stateful · 2026-08-08 13:44:25 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,220,412 · 10 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
1w05w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0xf8982aa7…cbbf
0x34b655…2a6f
4 touches
1 conflict
0x02fdb0e0…b418
0x34b655…2a6f
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x16cc2b0b…f774
0x34b655…2a6f
2 touches
0 conflicts
0x19e6dc50…6288
0x34b655…2a6f
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity