← previous blocknext block →recent activity
Analyzing
Block #100,917,114
17 transactions · 15 stateful · 2026-09-01 01:59:16 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,917,114 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5364309…7573
0x065c9d…c394
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x5da62519…5468
0xd32edf…ff58
5 touches
3 conflicts
0xc2aacf41…5502
0x1b6862…e19c
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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-MON/USDC
3 conflicts on slot 0xf536430949…5f7573
Audit this contract →
← previous block·next block →recent activity