← previous blocknext block →recent activity
Analyzing
Block #82,969,022
10 transactions · 8 stateful · 2026-06-22 14:10:08 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,969,022 · 10 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
1w02w13w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x31130c7e…0cc7
0x34b655…2a6f
6 touches
3 conflicts
0x36510b9c…90d2
0x34b655…2a6f
6 touches
3 conflicts
0x62db95d4…351c
0x34b655…2a6f
6 touches
3 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity