← previous blocknext block →recent activity
Analyzing
Block #83,853,978
10 transactions · 9 stateful · 2026-06-26 16:40:53 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,853,978 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0xb75cbfa3…6702
0x34b655…2a6f
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf4fd8105…fdc6
0x065c9d…c394
3 touches
1 conflict
0x55348eb1…0fb3
0x065c9d…c394
3 touches
1 conflict
0xc1f71778…a775
0x065c9d…c394
3 touches
1 conflict
0xef926822…4f43
0x065c9d…c394
3 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
1 conflict on slot 0x785889c9fb…160603
Audit this contract →
← previous block·next block →recent activity