← previous blocknext block →recent activity
Analyzing
Block #91,546,336
9 transactions · 8 stateful · 2026-07-30 05:28:46 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,546,336 · 9 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x334aa47d…cac0
0x34b655…2a6f
4 touches
1 conflict
0x4e412b57…4771
0x34b655…2a6f
4 touches
1 conflict
0x56902411…e0ce
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0cb0e57c…64c8
0x34b655…2a6f
2 touches
0 conflicts
0x0cbfe623…1409
0x34b655…2a6f
2 touches
0 conflicts
0x1bf8d2af…d140
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 0x334aa47d07…b9cac0
Audit this contract →
← previous block·next block →recent activity