← previous blocknext block →recent activity
Analyzing
Block #84,524,129
13 transactions · 10 stateful · 2026-06-29 19:06:37 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,524,129 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a3ae0e3…ac9b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb2cdadc7…d414
0x40c49f…2af0
2 touches
0 conflicts
0xb4cfbef1…2a21
0x40c49f…2af0
2 touches
0 conflicts
0xd1e5daff…ad66
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 0x3a3ae0e347…b0ac9b
Audit this contract →
← previous block·next block →recent activity