← previous blocknext block →recent activity
Analyzing
Block #84,254,439
34 transactions · 24 stateful · 2026-06-28 13:08:53 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,254,439 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w111w119w020w221w322w123w424w526w228w129w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x478e6e08…83bf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xa87df366…0824
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x478e6e0871…8083bf
Audit this contract →
← previous block·next block →recent activity