← previous blocknext block →recent activity
Analyzing
Block #92,761,996
11 transactions · 9 stateful · 2026-08-03 11:24:26 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,761,996 · 11 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc184ff1…fe6c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf009b1a8…d02d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0406a8bb…39a9
0x34b655…2a6f
4 touches
1 conflict
0x1efc452b…354f
0x34b655…2a6f
4 touches
1 conflict
0x1efc452b…3550
0x34b655…2a6f
4 touches
1 conflict
0x278c4ae5…1639
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
1 conflict on slot 0xcc184ff196…26fe6c
Audit this contract →
← previous block·next block →recent activity