← previous blocknext block →recent activity
Analyzing
Block #84,521,422
16 transactions · 15 stateful · 2026-06-29 18:48:37 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,521,422 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w08w19w210w311w412w414w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dbefc67…4855
0x34b655…2a6f
6 touches
3 conflicts
0xfff39462…a61b
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0x9906ae2c…90bb
0xd32edf…ff58
5 touches
3 conflicts
0x73912233…4587
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x187490f5…9924
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 0x9dbefc672a…064855
Audit this contract →
← previous block·next block →recent activity