← previous blocknext block →recent activity
Analyzing
Block #85,959,871
13 transactions · 11 stateful · 2026-07-06 10:36:30 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,959,871 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0xd4685965…3340
0x065c9d…c394
4 touches
1 conflict
0x89bd8d84…1d1b
0x065c9d…c394
4 touches
1 conflict
0x97d7410c…2015
0x065c9d…c394
3 touches
1 conflict
0x61745332…e032
0x065c9d…c394
3 touches
1 conflict
0xfab8b28c…a106
0x065c9d…c394
3 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
6 conflicts on slot 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity