← previous blocknext block →recent activity
Analyzing
Block #106,014,521
35 transactions · 28 stateful · 2026-09-18 22:50:09 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,014,521 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w08w19w210w311w412w519w320w423w528w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x18cf3003…51d1
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0x26253352…1a75
0x34b655…2a6f
6 touches
3 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity