← previous blocknext block →recent activity
Analyzing
Block #98,505,314
109 transactions · 55 stateful · 2026-08-23 14:42:48 UTC
Parallelism
84/100
Blocked
80%
Avg conflicts / tx
2.39
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,505,314 · 109 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w212w317w418w519w620w721w822w923w1024w1125w1226w1377w1078w1181w1282w1387w1488w1596w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
28 touches
91 conflicts
0x17606ba6…1b6e
0x754704…b603
26 touches
78 conflicts
0x5778d110…d2e6
0xc8689a…ee79
24 touches
66 conflicts
0x40970e69…da50
0x2b46c0…1669
24 touches
66 conflicts
0x00000000…003d
0xa6afd3…d132
24 touches
66 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
24 touches
66 conflicts
0x4ca87477…f8da
0xa6afd3…d132
22 touches
55 conflicts
0x56a919c4…ab49
0xee8c0e…1242
22 touches
55 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
91 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity