← previous blocknext block →recent activity
Analyzing
Block #92,806,120
20 transactions · 19 stateful · 2026-08-03 15:06:30 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,806,120 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w17w28w111w312w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1ed6769…ff4b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3cb07f3b…6e72
0x34b655…2a6f
4 touches
1 conflict
0x4a1261f9…46b8
0x34b655…2a6f
4 touches
1 conflict
0x575b141f…0cef
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 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity