← previous blocknext block →recent activity
Analyzing
Block #83,633,268
14 transactions · 13 stateful · 2026-06-25 16:08:11 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,633,268 · 14 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
1w02w03w14w26w07w18w19w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c2d3275…b647
0x34b655…2a6f
8 touches
6 conflicts
0xec85756f…0ba2
0x34b655…2a6f
8 touches
6 conflicts
0xe334a6b5…173c
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4abf223d…0915
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
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
6 conflicts on slot 0x4c2d3275b0…4fb647
Audit this contract →
← previous block·next block →recent activity