← previous blocknext block →recent activity
Analyzing
Block #84,364,293
14 transactions · 12 stateful · 2026-06-29 01:20:57 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,364,293 · 14 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
4w05w18w110w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b408000…9df1
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xb7a3240c…dd63
0x34b655…2a6f
4 touches
1 conflict
0x0ee4fe41…9382
0x34b655…2a6f
2 touches
0 conflicts
0x2b1b66e9…d1c4
0x34b655…2a6f
2 touches
0 conflicts
0x2d69c1bb…6b5e
0x34b655…2a6f
2 touches
0 conflicts
0x3817764d…242b
0x34b655…2a6f
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
3 conflicts on slot 0x0b4080004d…f59df1
Audit this contract →
← previous block·next block →recent activity