← previous blocknext block →recent activity
Analyzing
Block #85,973,744
29 transactions · 20 stateful · 2026-07-06 12:09:03 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,973,744 · 29 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
1w02w13w04w010w116w218w120w021w022w223w324w025w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7e10454f…4d9e
0xa6afd3…d132
6 touches
3 conflicts
0xb43dc900…22f2
0xa6afd3…d132
6 touches
3 conflicts
0xb20a6948…7da2
0xd32edf…ff58
5 touches
3 conflicts
0x58e06bab…34cd
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity