← previous blocknext block →recent activity
Analyzing
Block #86,082,881
30 transactions · 20 stateful · 2026-07-07 00:17:47 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,082,881 · 30 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
1w05w07w19w011w212w317w018w122w124w425w528w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x78cb41e1…f2c1
0xfa32f9…f3f0
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity