← previous blocknext block →recent activity
Analyzing
Block #82,965,660
16 transactions · 13 stateful · 2026-06-22 13:47:39 UTC
Parallelism
56/100
Blocked
46%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,965,660 · 16 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
4w05w18w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8544144c…131f
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0xd9a92b6a…01dc
0x34b655…2a6f
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x06c59b8c…89c0
0x34b655…2a6f
6 touches
3 conflicts
0xa62791bc…c2ec
0x34b655…2a6f
5 touches
4 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