← previous blocknext block →recent activity
Analyzing
Block #86,776,068
13 transactions · 11 stateful · 2026-07-10 05:30:55 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,776,068 · 13 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
1w02w04w05w06w17w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9e
0x34b655…2a6f
4 touches
1 conflict
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0x4247b8d6…46c6
0x34b655…2a6f
4 touches
1 conflict
0x5ff95106…7c15
0x34b655…2a6f
4 touches
1 conflict
0x5ff95106…7c16
0x34b655…2a6f
4 touches
1 conflict
0x6c7ca486…23f1
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity