← previous blocknext block →recent activity
Analyzing
Block #94,680,240
11 transactions · 9 stateful · 2026-08-10 04:29:08 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,680,240 · 11 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x5af6b453…0e18
0x34b655…2a6f
4 touches
1 conflict
0x2afe51f4…4006
0x34b655…2a6f
2 touches
0 conflicts
0x455cc08d…26b6
0x34b655…2a6f
2 touches
0 conflicts
0x684d81e4…89da
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 0x5da59c2b2f…b6d7b2
Audit this contract →
← previous block·next block →recent activity