← previous blocknext block →recent activity
Analyzing
Block #98,770,727
100 transactions · 45 stateful · 2026-08-24 13:32:56 UTC
Parallelism
82/100
Blocked
67%
Avg conflicts / tx
1.7
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #98,770,727 · 100 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w19w213w314w444w347w450w551w652w753w856w957w1058w1163w1266w1367w1471w1578w1690w392w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
34 touches
136 conflicts
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0x5b09bf44…5907
0xa6afd3…d132
20 touches
45 conflicts
0x10d80fee…dbda
0x2b46c0…1669
18 touches
36 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
18 touches
36 conflicts
0x5778d110…d2e6
0xc8689a…ee79
18 touches
36 conflicts
0xa987699f…eabe
0x2b46c0…1669
18 touches
36 conflicts
0x40970e69…da50
0x2b46c0…1669
18 touches
36 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 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity