← previous blocknext block →recent activity
Analyzing
Block #101,303,468
9 transactions · 9 stateful · 2026-09-02 10:23:18 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,303,468 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x7e95fe64…7024
0x851145…3f07
4 touches
1 conflict
0xf362e8a6…6ce6
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6e733b13…b909
0x851145…3f07
4 touches
1 conflict
0x72ed4d56…0a72
0x851145…3f07
3 touches
1 conflict
0xb75b2ed3…3674
0x851145…3f07
3 touches
1 conflict
0x915c095e…c1e5
0x34ae4d…3fc5
2 touches
0 conflicts
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