← previous blocknext block →recent activity
Analyzing
Block #106,539,053
40 transactions · 37 stateful · 2026-09-20 18:50:03 UTC
Parallelism
82/100
Blocked
49%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,539,053 · 40 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
2w04w07w18w210w112w013w014w015w116w217w318w019w320w122w224w331w433w534w637w139w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xcc8faac2…c766
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity