pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,100,049
← previous block
next block →
recent activity
Analyzing
Block #106,100,049
10 transactions · 9 stateful · 2026-09-19 06:00:34 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,100,049
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x5acec890
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x59558d29
#7
0x59558d29
#8
setData
#9
execOrders
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb127c451…050a
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b2
0x37db7f…ec7b
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x0f763490…ff64
0x34b655…2a6f
2 touches
0 conflicts
0x342cec45…b46d
0x34b655…2a6f
2 touches
0 conflicts
0x759e14fc…2ace
0x34b655…2a6f
2 touches
0 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:
0x37db7fbf…3eec7b
1 conflict on slot
0xb127c451ae…40050a
Audit this contract →
← previous block
·
next block →
recent activity