← previous blocknext block →recent activity
Analyzing
Block #83,660,722
18 transactions · 18 stateful · 2026-06-25 19:11:23 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,660,722 · 18 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
6w07w08w19w210w311w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x3ca49d36…1280
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
6 touches
3 conflicts
0x9b72b1df…57b4
0x34b655…2a6f
6 touches
3 conflicts
0x9f530e1d…c0ae
0x34b655…2a6f
6 touches
3 conflicts
0xdf37a93d…879b
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity