← previous blocknext block →recent activity
Analyzing
Block #82,712,701
13 transactions · 11 stateful · 2026-06-21 09:37:48 UTC
Parallelism
46/100
Blocked
55%
Avg conflicts / tx
1.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,712,701 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x1ebe108b…72a0
0x34b655…2a6f
6 touches
3 conflicts
0x71641e8d…a781
0x34b655…2a6f
6 touches
3 conflicts
0xa8b18ba0…f380
0x34b655…2a6f
5 touches
3 conflicts
0xdd53a1b8…791b
0x34b655…2a6f
5 touches
3 conflicts
0x7c0bdc54…9dde
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity