← previous blocknext block →recent activity
Analyzing
Block #106,031,297
17 transactions · 16 stateful · 2026-09-19 00:14:34 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,031,297 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w311w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xb1911d11…2ff1
0x34b655…2a6f
4 touches
1 conflict
0xaa656c5f…b856
0x34b655…2a6f
4 touches
1 conflict
0x885efce3…7496
0x34b655…2a6f
4 touches
1 conflict
0x52b0bc2b…1305
0x34b655…2a6f
4 touches
1 conflict
0xfa5cc44b…5c91
0xd32edf…ff58
3 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
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity