← previous blocknext block →recent activity
Analyzing
Block #98,505,264
114 transactions · 56 stateful · 2026-08-23 14:42:32 UTC
Parallelism
84/100
Blocked
75%
Avg conflicts / tx
1.88
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #98,505,264 · 114 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
1w02w13w24w312w470w171w272w373w474w575w676w777w878w979w1080w1181w1282w1385w486w1489w590w1599w6104w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
32 touches
120 conflicts
0x00000000…003d
0xa6afd3…d132
28 touches
91 conflicts
0x65021fef…b735
0xa6afd3…d132
26 touches
78 conflicts
0xdb067026…9eb8
0x2b46c0…1669
24 touches
66 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
24 touches
66 conflicts
0x55012d1a…3907
0x2b46c0…1669
24 touches
66 conflicts
0x40970e69…da50
0x2b46c0…1669
24 touches
66 conflicts
0x5778d110…d2e6
0xc8689a…ee79
24 touches
66 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
120 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity