← previous blocknext block →recent activity
Analyzing
Block #86,395,096
19 transactions · 19 stateful · 2026-07-08 11:02:43 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,395,096 · 19 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
1w011w114w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0x0de989de…af9a
0x065c9d…c394
2 touches
0 conflicts
0x46c8a620…ecdc
0x065c9d…c394
2 touches
0 conflicts
0x554a9824…9013
0x065c9d…c394
2 touches
0 conflicts
0x5ccbd043…1147
0x065c9d…c394
2 touches
0 conflicts
0x611a4030…c327
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity