← previous blocknext block →recent activity
Analyzing
Block #86,331,095
17 transactions · 16 stateful · 2026-07-08 03:55:05 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,331,095 · 17 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
1w03w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3255235a…d360
0x065c9d…c394
2 touches
0 conflicts
0xae29267b…14c8
0x065c9d…c394
2 touches
0 conflicts
0xbd12130b…9410
0x065c9d…c394
2 touches
0 conflicts
0xbf1d9fe5…d411
0x065c9d…c394
2 touches
0 conflicts
0xc37feee8…da4b
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity