← previous blocknext block →recent activity
Analyzing
Block #83,410,298
27 transactions · 21 stateful · 2026-06-24 15:20:06 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.15
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,410,298 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w310w011w112w213w314w415w516w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x901d9f30…67a4
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xec7b070f…db9a
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0xadbfba07…4e41
0xd32edf…ff58
5 touches
3 conflicts
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity