← previous blocknext block →recent activity
Analyzing
Block #99,450,749
18 transactions · 17 stateful · 2026-08-26 22:41:45 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,450,749 · 18 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
1w02w13w08w09w111w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x1e9e299e…713c
0x34b655…2a6f
4 touches
1 conflict
0x4387ba94…e195
0x34b655…2a6f
2 touches
0 conflicts
0x64098689…15d5
0x34b655…2a6f
2 touches
0 conflicts
0x845ec8b0…c1af
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
1 conflict on slot 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity