← previous blocknext block →recent activity
Analyzing
Block #84,539,522
25 transactions · 23 stateful · 2026-06-29 20:49:14 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,539,522 · 25 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
2w03w14w29w010w011w112w214w219w020w322w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x70638c24…1553
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x85a88798…f85e
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: 0xd637b38f…c64160
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity