← previous blocknext block →recent activity
Analyzing
Block #83,901,976
16 transactions · 14 stateful · 2026-06-26 22:01:05 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,901,976 · 16 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
1w02w13w04w25w18w210w211w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x8e739938…e7ab
0x34b655…2a6f
6 touches
3 conflicts
0x398e65c6…4573
0xa6afd3…d132
5 touches
3 conflicts
0xec656e7d…4971
0xd32edf…ff58
5 touches
3 conflicts
0x07b5c6c6…8863
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity