← previous blocknext block →recent activity
Analyzing
Block #99,121,688
12 transactions · 12 stateful · 2026-08-25 19:05:36 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,121,688 · 12 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
1w03w04w15w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5007bc8…6005
0x065c9d…c394
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x8237ea2c…f3cf
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
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
1 conflict on slot 0xe5007bc817…ea6005
Audit this contract →
← previous block·next block →recent activity