← previous blocknext block →recent activity
Analyzing
Block #101,325,513
36 transactions · 26 stateful · 2026-09-02 12:14:14 UTC
Parallelism
89/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,325,513 · 36 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
1w06w17w28w39w312w013w014w115w116w018w126w227w028w229w230w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5095cb33…2491
0xa6afd3…d132
6 touches
3 conflicts
0xa13db997…2a7a
0x34b655…2a6f
6 touches
3 conflicts
0xe8f5e33f…719c
0x34b655…2a6f
6 touches
3 conflicts
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0xb4eeffcf…1bf3
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