← previous blocknext block →recent activity
Analyzing
Block #98,332,251
48 transactions · 35 stateful · 2026-08-23 00:10:36 UTC
Parallelism
83/100
Blocked
51%
Avg conflicts / tx
0.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,332,251 · 48 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
2w03w07w19w119w020w121w222w023w124w229w230w331w432w333w434w538w439w540w645w546w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x16ebf93b…ce00
0x34b655…2a6f
6 touches
3 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity