← previous blocknext block →recent activity
Analyzing
Block #83,454,685
20 transactions · 18 stateful · 2026-06-24 20:16:36 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,454,685 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w08w19w210w011w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x126a0344…4465
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x02dfdb6c…0ebe
0x34b655…2a6f
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0xe9425fe7…1711
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
3 conflicts on slot 0x126a0344b1…d04465
Audit this contract →
← previous block·next block →recent activity