← previous blocknext block →recent activity
Analyzing
Block #99,111,402
18 transactions · 18 stateful · 2026-08-25 18:13:44 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,111,402 · 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
1w02w04w06w17w29w110w211w013w114w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76cb339c…4198
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b69cc9b…2aca
0x34b655…2a6f
4 touches
1 conflict
0x39ccd26a…4654
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x76cb339c69…da4198
Audit this contract →
← previous block·next block →recent activity