← previous blocknext block →recent activity
Analyzing
Block #106,042,028
35 transactions · 27 stateful · 2026-09-19 01:08:35 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,042,028 · 35 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
1w02w13w24w06w07w08w113w117w218w123w024w325w228w131w332w433w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity