← previous blocknext block →recent activity
Analyzing
Block #98,768,372
19 transactions · 17 stateful · 2026-08-24 13:21:06 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,768,372 · 19 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
1w02w13w24w05w06w18w29w010w311w112w417w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x2a5499c6…0abf
0xa6afd3…d132
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4f458401…2b41
0x851145…3f07
4 touches
1 conflict
0xa52ff19e…48b2
0x851145…3f07
4 touches
1 conflict
0xae3ebcf3…3b04
0x851145…3f07
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity