← previous blocknext block →recent activity
Analyzing
Block #98,753,243
20 transactions · 20 stateful · 2026-08-24 12:04:54 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,753,243 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w08w29w310w411w512w613w214w115w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x513e7e8d…9475
0x40c49f…2af0
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc9a06450…d07e
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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
21 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity