← previous blocknext block →recent activity
Analyzing
Block #99,087,232
24 transactions · 23 stateful · 2026-08-25 16:12:03 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,087,232 · 24 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
1w04w05w06w114w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b45fd6…4a0d
0x065c9d…c394
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x382069a7…bc58
0x065c9d…c394
3 touches
1 conflict
0x22329896…72c3
0x065c9d…c394
3 touches
1 conflict
0x1f5a2e2b…65f1
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9355
0x2b46c0…1669
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 0xb6b45fd68e…b04a0d
Audit this contract →
← previous block·next block →recent activity