← previous blocknext block →recent activity
Analyzing
Block #98,642,014
14 transactions · 14 stateful · 2026-08-24 02:35:22 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,642,014 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w28w39w111w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2274142b…f885
0x851145…3f07
4 touches
1 conflict
0x7ea2bdd4…b4b0
0x851145…3f07
4 touches
1 conflict
0x8b98c194…d69e
0x851145…3f07
4 touches
1 conflict
0x8ed70c47…59cd
0x065c9d…c394
3 touches
1 conflict
0xbeaa9aff…cef5
0xd32edf…ff58
3 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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity