← previous blocknext block →recent activity
Analyzing
Block #98,753,984
16 transactions · 16 stateful · 2026-08-24 12:08:39 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,753,984 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w39w410w511w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
14 touches
21 conflicts
0x18546585…888c
0x40c49f…2af0
13 touches
21 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd5443218…4257
0x40c49f…2af0
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x06ce5d4b…c122
0x2b46c0…1669
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 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity