← previous blocknext block →recent activity
Analyzing
Block #98,839,326
25 transactions · 25 stateful · 2026-08-24 19:18:17 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,839,326 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w111w114w015w217w218w322w023w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8e66da19…66b6
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x33000c0a…82c3
0x34b655…2a6f
4 touches
1 conflict
0x8ab32918…c83c
0x34b655…2a6f
4 touches
1 conflict
0x9d22c394…c125
0x34b655…2a6f
4 touches
1 conflict
0xb75d08b2…3e12
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