← previous blocknext block →recent activity
Analyzing
Block #100,923,505
29 transactions · 23 stateful · 2026-09-01 02:31:25 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,923,505 · 29 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
1w04w15w27w38w411w018w020w121w023w124w225w526w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xed7dd7db…6022
0x34ae4d…3fc5
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x71fad9ce…c11f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: MarginAccount
6 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity