← previous blocknext block →recent activity
Analyzing
Block #100,922,729
14 transactions · 14 stateful · 2026-09-01 02:27:31 UTC
Parallelism
64/100
Blocked
29%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,922,729 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7c6f0ea…f514
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2e69ac38…50e5
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0xe7c6f0ea…f515
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xe7c6f0ea1f…cbf514
Audit this contract →
← previous block·next block →recent activity