← previous blocknext block →recent activity
Analyzing
Block #84,510,721
12 transactions · 11 stateful · 2026-06-29 17:37:15 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,510,721 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9180af06…5ac6
0x34b655…2a6f
4 touches
1 conflict
0x97fe3267…5e87
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x18497d38…c3b3
0x40c49f…2af0
2 touches
0 conflicts
0x774b21fc…1488
0x40c49f…2af0
2 touches
0 conflicts
0x82234598…4354
0x40c49f…2af0
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
1 conflict on slot 0x9180af06f8…7e5ac6
Audit this contract →
← previous block·next block →recent activity