← previous blocknext block →recent activity
Analyzing
Block #85,900,814
10 transactions · 7 stateful · 2026-07-06 04:02:50 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,900,814 · 10 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
1w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x116dfc66…9435
0x065c9d…c394
2 touches
0 conflicts
0x40f77d3f…401f
0x065c9d…c394
2 touches
0 conflicts
0x49e46974…777c
0x065c9d…c394
2 touches
0 conflicts
0x6efa8ab9…1fc3
0x065c9d…c394
2 touches
0 conflicts
0x83cd8cf1…a34e
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
1 conflict on slot 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity