← previous blocknext block →recent activity
Analyzing
Block #105,403,309
26 transactions · 19 stateful · 2026-09-16 19:31:25 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,403,309 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w09w210w311w112w215w018w421w523w624w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x305e45b5…fbdd
0xa6afd3…d132
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x29be38f0…7bb1
0x40c49f…2af0
4 touches
1 conflict
0xa149f0ce…4d65
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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