← previous blocknext block →recent activity
Analyzing
Block #82,018,489
160 transactions · 12 stateful · 2026-06-18 04:23:16 UTC
Parallelism
96/100
Blocked
42%
Avg conflicts / tx
0.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,018,489 · 160 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
54w080w188w2103w3106w4108w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
12 touches
15 conflicts
0xf13f45b3…7a9b
0x34b655…2a6f
6 touches
3 conflicts
0x1086ec16…1a17
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x5701e33e…a3fe
0x34b655…2a6f
4 touches
1 conflict
0x9c7ce5c3…2a4e
0x34b655…2a6f
4 touches
1 conflict
0xf6f9554c…ae47
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
15 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity