← previous blocknext block →recent activity
Analyzing
Block #91,189,254
10 transactions · 9 stateful · 2026-07-28 23:30:02 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,189,254 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x0c7a4619…2b80
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x3d282021…f942
0x34b655…2a6f
2 touches
0 conflicts
0x5b063601…162e
0x34b655…2a6f
2 touches
0 conflicts
0x6e6b8ec7…2197
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 0x1321736a95…4043e3
Audit this contract →
← previous block·next block →recent activity