← previous blocknext block →recent activity
Analyzing
Block #106,395,109
20 transactions · 19 stateful · 2026-09-20 06:45:34 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,395,109 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w010w011w012w113w114w216w317w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d6ad769…5d2e
0x34b655…2a6f
10 touches
10 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
8 touches
6 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0xb1927b58…f161
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x045532dd…4b7d
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: Perpl
10 conflicts on slot 0x2d6ad76908…225d2e
Audit this contract →
← previous block·next block →recent activity