← previous blocknext block →recent activity
Analyzing
Block #91,259,930
6 transactions · 5 stateful · 2026-07-29 05:25:39 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,259,930 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2ce84d2…4c5a
0x34b655…2a6f
4 touches
1 conflict
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0e16ea14…6144
0x34b655…2a6f
2 touches
0 conflicts
0x10183c49…f952
0x34b655…2a6f
2 touches
0 conflicts
0x15144de9…722d
0x34b655…2a6f
2 touches
0 conflicts
0x1e3dc02f…b1ba
0x34b655…2a6f
2 touches
0 conflicts
0x1e3dc02f…b1bb
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 0xb2ce84d2d9…844c5a
Audit this contract →
← previous block·next block →recent activity