← previous blocknext block →recent activity
Analyzing
Block #92,564,319
13 transactions · 11 stateful · 2026-08-02 18:49:02 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,564,319 · 13 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
2w03w05w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0x404494d0…f3d9
0x34b655…2a6f
6 touches
3 conflicts
0x57330c5d…9973
0x34b655…2a6f
6 touches
3 conflicts
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x3eacdae2…6436
0x34b655…2a6f
4 touches
1 conflict
0x3efad0b5…b0a8
0x34b655…2a6f
4 touches
1 conflict
0x3efad0b5…b0a9
0x34b655…2a6f
4 touches
1 conflict
0x50887223…db7f
0x34b655…2a6f
4 touches
1 conflict
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 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity