← previous blocknext block →recent activity
Analyzing
Block #105,470,613
32 transactions · 26 stateful · 2026-09-17 01:10:09 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,470,613 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w37w08w110w011w112w114w215w316w421w422w523w630w631w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
8 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0x648bb928…97f2
0x34b655…2a6f
8 touches
6 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 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: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity