← previous blocknext block →recent activity
Analyzing
Block #82,967,575
22 transactions · 17 stateful · 2026-06-22 14:00:28 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,967,575 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w17w213w214w117w219w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52342825…6e5c
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 conflicts
0xbd7e0241…07f5
0x34b655…2a6f
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0xd5a3236b…6b26
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
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
3 conflicts on slot 0x5234282554…2d6e5c
Audit this contract →
← previous block·next block →recent activity