← previous blocknext block →recent activity
Analyzing
Block #82,793,427
24 transactions · 17 stateful · 2026-06-21 18:36:35 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,793,427 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w110w011w112w215w217w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc68d6f14…bdde
0x34b655…2a6f
6 touches
3 conflicts
0x9fb55ee7…8ecc
0xa6afd3…d132
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0x4c99e7ce…47e4
0x34b655…2a6f
4 touches
1 conflict
0x56d04b30…74bb
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity