← previous blocknext block →recent activity
Analyzing
Block #99,203,392
18 transactions · 16 stateful · 2026-08-26 01:56:39 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,203,392 · 18 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
2w03w05w111w112w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7decbd8e…2442
0x8964d7…10f8
4 touches
1 conflict
0x145ff925…9da0
0x8964d7…10f8
4 touches
1 conflict
0x145ff925…9da1
0x8964d7…10f8
4 touches
1 conflict
0x145ff925…9da3
0x8964d7…10f8
4 touches
1 conflict
0x7decbd8e…243f
0x8964d7…10f8
4 touches
1 conflict
0x7decbd8e…2440
0x8964d7…10f8
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
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