← previous blocknext block →recent activity
Analyzing
Block #105,462,009
35 transactions · 27 stateful · 2026-09-17 00:26:51 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,462,009 · 35 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
2w04w15w26w38w39w411w314w015w017w018w122w125w226w528w629w732w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x36743f6f…476b
0x3bd359…433a
8 touches
6 conflicts
0xe31cf99d…cb66
0x754704…b603
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
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: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity