← previous blocknext block →recent activity
Analyzing
Block #92,061,260
35 transactions · 35 stateful · 2026-08-01 00:39:01 UTC
Parallelism
91/100
Blocked
9%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,061,260 · 35 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
3w05w030w132w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdadee63d…484c
0x34b655…2a6f
6 touches
3 conflicts
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5555c0cb…d686
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x260eb524…8a3e
0x34b655…2a6f
4 touches
1 conflict
0x4cd46947…fbd9
0x34b655…2a6f
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
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
3 conflicts on slot 0xdadee63d4e…f2484c
Audit this contract →
← previous block·next block →recent activity