← previous blocknext block →recent activity
Analyzing
Block #98,208,291
21 transactions · 21 stateful · 2026-08-22 13:46:56 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,208,291 · 21 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
1w03w04w05w08w09w010w111w112w113w214w115w116w218w319w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb3037bed…6b7c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x1fd77335…9120
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x5b7e8e52…6e30
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
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