← previous blocknext block →recent activity
Analyzing
Block #99,251,548
10 transactions · 9 stateful · 2026-08-26 05:58:55 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,251,548 · 10 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
1w02w14w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x8b98c194…d69e
0x851145…3f07
4 touches
1 conflict
0xeffd747c…6a01
0x851145…3f07
4 touches
1 conflict
0x93476e49…09ed
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0xbe31a61f…f5bf
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity