← previous blocknext block →recent activity
Analyzing
Block #101,310,905
25 transactions · 25 stateful · 2026-09-02 11:00:44 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,310,905 · 25 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
2w03w15w06w07w112w114w015w116w219w120w222w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde5c131f…da2c
0xa6afd3…d132
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x8571fbdb…345a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa1731f0f…1f9d
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-WETH/USDC
3 conflicts on slot 0xde5c131f97…8fda2c
Audit this contract →
← previous block·next block →recent activity