← previous blocknext block →recent activity
Analyzing
Block #98,492,039
18 transactions · 16 stateful · 2026-08-23 13:34:51 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,492,039 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w38w49w512w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x93bf91d2…3eee
0xd32edf…ff58
5 touches
3 conflicts
0x6d43ee99…bdd7
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity