← previous blocknext block →recent activity
Analyzing
Block #82,965,821
15 transactions · 14 stateful · 2026-06-22 13:48:44 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,965,821 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c59b8c…89c0
0x34b655…2a6f
4 touches
1 conflict
0xa62791bc…c2ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xb4c35fcd…43ae
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0ea930f5…6109
0x34b655…2a6f
2 touches
0 conflicts
0x9b93731a…451c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x06c59b8c41…2989c0
Audit this contract →
← previous block·next block →recent activity