← previous blocknext block →recent activity
Analyzing
Block #86,688,384
32 transactions · 24 stateful · 2026-07-09 19:45:17 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,688,384 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w011w115w016w117w118w222w224w225w326w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x1f3d3ba6…4177
0xd32edf…ff58
5 touches
3 conflicts
0xf0b015b0…ca88
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
0x1b6862…e19c
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