← previous blocknext block →recent activity
Analyzing
Block #86,250,325
27 transactions · 23 stateful · 2026-07-07 18:55:50 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,250,325 · 27 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
2w03w14w25w37w08w19w210w311w012w116w017w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xcade7e5a…2903
0xd32edf…ff58
7 touches
6 conflicts
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0xcf94f773…2dae
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity