← previous blocknext block →recent activity
Analyzing
Block #106,207,643
30 transactions · 23 stateful · 2026-09-19 15:02:06 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,207,643 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w08w111w012w120w121w122w123w224w325w227w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x74fa9cc0…c570
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 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: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity