← previous blocknext block →recent activity
Analyzing
Block #86,083,132
12 transactions · 9 stateful · 2026-07-07 00:19:27 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,083,132 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x1a93f669…cc73
0x065c9d…c394
3 touches
1 conflict
0x4036e360…62b1
0x065c9d…c394
2 touches
0 conflicts
0x603ed215…bc56
0x065c9d…c394
2 touches
0 conflicts
0x8d883caf…f547
0x065c9d…c394
2 touches
0 conflicts
0x999ab46b…6a11
0x065c9d…c394
2 touches
0 conflicts
0xa4455877…1c1a
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity