← previous blocknext block →recent activity
Analyzing
Block #82,970,573
28 transactions · 21 stateful · 2026-06-22 14:20:30 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,970,573 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w115w218w020w121w222w323w424w526w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
0xab3ba25f…ec78
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x830b63a6…8105
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xc37eb1c4…b0b1
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity