← previous blocknext block →recent activity
Analyzing
Block #84,498,853
17 transactions · 16 stateful · 2026-06-29 16:18:02 UTC
Parallelism
76/100
Blocked
19%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,498,853 · 17 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
4w06w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a8f8b9c…3046
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x1564aef8…90c9
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
0x34b655…2a6f
2 touches
0 conflicts
0xab86573c…682e
0x34b655…2a6f
2 touches
0 conflicts
0xc0ea9bd0…16ce
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x0a8f8b9c32…e53046
Audit this contract →
← previous block·next block →recent activity