← previous blocknext block →recent activity
Analyzing
Block #91,822,300
6 transactions · 6 stateful · 2026-07-31 04:36:58 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,822,300 · 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
2w03w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3c96942…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2477d0da…f68e
0x34b655…2a6f
4 touches
1 conflict
0xacf2813c…1964
0x34b655…2a6f
4 touches
1 conflict
0x72c8aeb2…9921
0x34b655…2a6f
2 touches
0 conflicts
0xa4e9800f…4ab1
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 0xb3c9694250…dbf0fc
Audit this contract →
← previous block·next block →recent activity