← previous blocknext block →recent activity
Analyzing
Block #98,499,259
108 transactions · 52 stateful · 2026-08-23 14:11:18 UTC
Parallelism
80/100
Blocked
83%
Avg conflicts / tx
2.72
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #98,499,259 · 108 txs across 22 waves · depth 22
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
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w48w514w530w636w737w838w996w1997w2099w21
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
40 touches
190 conflicts
0x38963aeb…c33f
0xa6afd3…d132
38 touches
171 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
34 touches
136 conflicts
0x10d80fee…dbda
0x2b46c0…1669
34 touches
136 conflicts
0x40970e69…da50
0x2b46c0…1669
34 touches
136 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
34 touches
136 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
34 touches
136 conflicts
0x39773cec…38ed
0xa6afd3…d132
34 touches
136 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
190 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity