← previous blocknext block →recent activity
Analyzing
Block #100,786,468
24 transactions · 23 stateful · 2026-08-31 15:01:50 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,786,468 · 24 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
1w02w03w15w26w37w410w011w115w016w117w520w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x76622fb2…4f08
0x34b655…2a6f
6 touches
3 conflicts
0x38963aeb…c33f
0xa6afd3…d132
6 touches
3 conflicts
0x39773cec…38ed
0xa6afd3…d132
6 touches
3 conflicts
0xe2263bea…6a9d
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6a9e
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6a9f
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: Kuru Exchange: MarginAccount
10 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity