← previous blocknext block →recent activity
Analyzing
Block #82,572,128
22 transactions · 15 stateful · 2026-06-20 17:56:34 UTC
Parallelism
64/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,572,128 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w410w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x2bab24a6…c56d
0x34b655…2a6f
2 touches
0 conflicts
0x599d8693…45ef
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
21 conflicts on slot 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity