← previous blocknext block →recent activity
Analyzing
Block #85,972,917
56 transactions · 41 stateful · 2026-07-06 12:03:31 UTC
Parallelism
66/100
Blocked
71%
Avg conflicts / tx
3.39
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,972,917 · 56 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w1321w1422w1523w1643w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
34 touches
136 conflicts
0x9da6e429…074d
0xa6afd3…d132
32 touches
120 conflicts
0x00000000…003d
0xa6afd3…d132
32 touches
120 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
30 touches
105 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
30 touches
105 conflicts
0x10d80fee…dbda
0x69df8a…6292
30 touches
105 conflicts
0x55012d1a…3907
0x69df8a…6292
30 touches
105 conflicts
0xa987699f…eabe
0x69df8a…6292
30 touches
105 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: MarginAccount
136 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity