← previous blocknext block →recent activity
Analyzing
Block #104,704,139
13 transactions · 13 stateful · 2026-09-14 08:50:09 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,704,139 · 13 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
1w02w13w28w29w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa396b64d…d395
0x40c49f…2af0
4 touches
1 conflict
0xad9c2f74…503d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6e733b13…b909
0x851145…3f07
4 touches
1 conflict
0xf362e8a6…6ce6
0x851145…3f07
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity