← previous blocknext block →recent activity
Analyzing
Block #106,192,745
36 transactions · 27 stateful · 2026-09-19 13:47:04 UTC
Parallelism
89/100
Blocked
30%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,192,745 · 36 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
5w08w012w014w118w119w221w129w231w334w135w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
6 touches
3 conflicts
0x8918384e…c413
0x34b655…2a6f
6 touches
3 conflicts
0xa29cba63…8030
0x34b655…2a6f
6 touches
3 conflicts
0xa3ff1ab2…8ae3
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
6 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity