← previous blocknext block →recent activity
Analyzing
Block #83,659,080
20 transactions · 20 stateful · 2026-06-25 19:00:28 UTC
Parallelism
60/100
Blocked
45%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,659,080 · 20 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
1w02w14w05w16w27w38w414w517w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cc5ec3…ae0e
0x34b655…2a6f
14 touches
21 conflicts
0x63f8a50d…333b
0x34b655…2a6f
12 touches
15 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
8 touches
6 conflicts
0xbb115a79…75ce
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xe732567d…b65d
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 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 0x17cc5ec39e…57ae0e
Audit this contract →
← previous block·next block →recent activity