← previous blocknext block →recent activity
Analyzing
Block #101,307,304
23 transactions · 18 stateful · 2026-09-02 10:42:37 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,307,304 · 23 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
1w03w17w08w19w212w017w319w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x6e733b13…b909
0x851145…3f07
6 touches
3 conflicts
0x7e95fe64…7024
0x851145…3f07
6 touches
3 conflicts
0xf362e8a6…6ce6
0x851145…3f07
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity