← previous blocknext block →recent activity
Analyzing
Block #101,248,817
18 transactions · 17 stateful · 2026-09-02 05:48:20 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,248,817 · 18 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x68106229…7057
0xa6afd3…d132
4 touches
1 conflict
0x0b104f98…d9ee
0xc8689a…ee79
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xabde8104…c9a9
0x2a68ba…90c5
4 touches
1 conflict
0xa987699f…eabe
0x34ae4d…3fc5
4 touches
1 conflict
0xad3ef711…4f2b
0x34ae4d…3fc5
4 touches
1 conflict
0xea7ebe9d…709e
0x34ae4d…3fc5
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-WETH/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity