← previous blocknext block →recent activity
Analyzing
Block #82,650,173
28 transactions · 19 stateful · 2026-06-21 02:39:41 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,650,173 · 28 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
2w04w05w112w013w119w121w224w025w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bf5914f…c75d
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x55ea4dd1…7ba2
0x34b655…2a6f
6 touches
3 conflicts
0x21e43e72…d2f6
0x34b655…2a6f
4 touches
1 conflict
0x26abe30c…f680
0x34b655…2a6f
4 touches
1 conflict
0x3b0a8356…a2b6
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
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
10 conflicts on slot 0x2bf5914fac…c4c75d
Audit this contract →
← previous block·next block →recent activity