← previous blocknext block →recent activity
Analyzing
Block #85,974,035
11 transactions · 10 stateful · 2026-07-06 12:11:00 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,974,035 · 11 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
1w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x22fc0930…90ef
0x065c9d…c394
2 touches
0 conflicts
0xc4892d3c…8a71
0x065c9d…c394
2 touches
0 conflicts
0xd8530bd6…b22f
0x065c9d…c394
2 touches
0 conflicts
0xf38ca652…2bda
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity