← previous blocknext block →recent activity
Analyzing
Block #86,056,814
21 transactions · 17 stateful · 2026-07-06 21:24:02 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,056,814 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w012w114w218w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x4aaf1f3d…633b
0x065c9d…c394
2 touches
0 conflicts
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0x8f9a894e…0a2f
0x065c9d…c394
2 touches
0 conflicts
0xfdaeec49…3cd2
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity