← previous blocknext block →recent activity
Analyzing
Block #83,670,800
19 transactions · 18 stateful · 2026-06-25 20:18:37 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,670,800 · 19 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
5w06w19w210w311w413w515w016w517w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1274880c…3cdc
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x7b73bda8…3b77
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13c5b486…d41e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x60872583…6452
0x34b655…2a6f
6 touches
3 conflicts
0x65df2980…8edc
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
15 conflicts on slot 0x1274880c39…5c3cdc
Audit this contract →
← previous block·next block →recent activity