← previous blocknext block →recent activity
Analyzing
Block #86,775,170
15 transactions · 11 stateful · 2026-07-10 05:24:56 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,775,170 · 15 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
1w03w04w07w18w09w011w112w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x283c0899…c778
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x31e46b94…8b6e
0x34b655…2a6f
4 touches
1 conflict
0x3a3a4219…6238
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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
1 conflict on slot 0x283c089903…e4c778
Audit this contract →
← previous block·next block →recent activity