← previous blocknext block →recent activity
Analyzing
Block #97,898,074
16 transactions · 16 stateful · 2026-08-21 11:39:49 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,898,074 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w07w08w19w210w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5095cb33…2491
0xa6afd3…d132
6 touches
3 conflicts
0xe22455da…1ce1
0x34b655…2a6f
4 touches
1 conflict
0x2f44258c…5abc
0x34b655…2a6f
2 touches
0 conflicts
0x41be9e75…9773
0x34b655…2a6f
2 touches
0 conflicts
0x43d7bda1…2c74
0x34b655…2a6f
2 touches
0 conflicts
0x6441ec14…715a
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity