← previous blocknext block →recent activity
Analyzing
Block #83,660,573
17 transactions · 14 stateful · 2026-06-25 19:10:23 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,660,573 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x2924b99d…372a
0x065c9d…c394
2 touches
0 conflicts
0x4ec67406…6f47
0x065c9d…c394
2 touches
0 conflicts
0x7f301aa0…4761
0x065c9d…c394
2 touches
0 conflicts
0xc1761112…fd0d
0x065c9d…c394
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
1 conflict on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity