← previous blocknext block →recent activity
Analyzing
Block #98,560,173
66 transactions · 63 stateful · 2026-08-23 19:29:02 UTC
Parallelism
97/100
Blocked
5%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,560,173 · 66 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w059w061w162w165w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3981be5…2c47
0x34b655…2a6f
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0x5bf80935…5e25
0x065c9d…c394
3 touches
1 conflict
0x2b942933…010a
0x065c9d…c394
3 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity