← previous blocknext block →recent activity
Analyzing
Block #82,703,372
20 transactions · 16 stateful · 2026-06-21 08:35:30 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,703,372 · 20 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
1w02w13w26w07w18w29w313w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1865516…fa1e
0x34b655…2a6f
8 touches
6 conflicts
0xf9f48af5…4205
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x69df8a…6292
6 touches
3 conflicts
0x26470289…bb21
0xa6afd3…d132
6 touches
3 conflicts
0x803beb89…d606
0xa6afd3…d132
6 touches
3 conflicts
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
6 conflicts on slot 0xa18655162e…6dfa1e
Audit this contract →
← previous block·next block →recent activity