← previous blocknext block →recent activity
Analyzing
Block #86,053,817
27 transactions · 23 stateful · 2026-07-06 21:04:04 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,053,817 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w38w412w016w117w518w623w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf68ab86d…bd08
0xd32edf…ff58
5 touches
3 conflicts
0x40c85d99…fb31
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity