← previous blocknext block →recent activity
Analyzing
Block #86,102,888
30 transactions · 24 stateful · 2026-07-07 02:31:18 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,102,888 · 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
3w05w16w08w19w210w312w013w124w325w226w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x30f8f558…68a8
0x065c9d…c394
5 touches
3 conflicts
0xb100cc92…2761
0x34b655…2a6f
4 touches
1 conflict
0xb7941802…c590
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity