← previous blocknext block →recent activity
Analyzing
Block #86,690,687
18 transactions · 13 stateful · 2026-07-09 20:00:38 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,690,687 · 18 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
1w03w16w07w114w015w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa4368bad…5eba
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x02c4bb0f…f2c8
0x34b655…2a6f
4 touches
1 conflict
0x04105a34…6eea
0x34b655…2a6f
4 touches
1 conflict
0x111d8a5f…7fa1
0x34b655…2a6f
4 touches
1 conflict
0x1929338b…cd11
0x34b655…2a6f
4 touches
1 conflict
0x1bfc029c…f91e
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity