← previous blocknext block →recent activity
Analyzing
Block #85,843,569
13 transactions · 11 stateful · 2026-07-05 21:41:26 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,843,569 · 13 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
1w02w15w09w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8f46b7d8…b63d
0x5afd3e…7620
4 touches
1 conflict
0x63ece9d1…0c48
0x5afd3e…7620
4 touches
1 conflict
0xac98159f…2a7b
0x065c9d…c394
4 touches
1 conflict
0x0e2cd8c3…90a8
0xd32edf…ff58
3 touches
1 conflict
0x287469ce…4c6b
0x065c9d…c394
3 touches
1 conflict
0x3319fcd9…ee8d
0x065c9d…c394
3 touches
1 conflict
0xdf81ad85…9743
0x010592…1c83
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity