← previous blocknext block →recent activity
Analyzing
Block #100,894,786
14 transactions · 14 stateful · 2026-09-01 00:06:58 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,894,786 · 14 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
3w04w15w06w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb737c509…603f
0x065c9d…c394
6 touches
3 conflicts
0x8764aa70…1d9c
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0001ec04…e7a5
0x065c9d…c394
3 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
2 touches
0 conflicts
0xf371c34e…e4ac
0x754704…b603
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
3 conflicts on slot 0xb737c5096b…dc603f
Audit this contract →
← previous block·next block →recent activity