← previous blocknext block →recent activity
Analyzing
Block #86,359,783
18 transactions · 12 stateful · 2026-07-08 07:06:39 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,359,783 · 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6035e80e…3c9c
0x065c9d…c394
3 touches
1 conflict
0xb0ba2be9…4fb1
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x07531b47…8c8e
0x065c9d…c394
2 touches
0 conflicts
0x1a499b19…cbc6
0x065c9d…c394
2 touches
0 conflicts
0x1feac008…4cf4
0x065c9d…c394
2 touches
0 conflicts
0x88c57a99…9978
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 0x6035e80e4e…713c9c
Audit this contract →
← previous block·next block →recent activity