← previous blocknext block →recent activity
Analyzing
Block #101,247,888
21 transactions · 20 stateful · 2026-09-02 05:43:40 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,247,888 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w26w37w08w19w410w011w112w113w315w520w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x3c13990d…642b
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
8 touches
6 conflicts
0x7d008e6d…ba40
0x40c49f…2af0
6 touches
3 conflicts
0x3e4576ad…2f3c
0x40c49f…2af0
4 touches
2 conflicts
0x6eff310a…c34c
0x34ae4d…3fc5
4 touches
1 conflict
0x7f4a8466…f2cc
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: 0x40c49f17…d22af0
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity