pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,100,077
← previous block
next block →
recent activity
Analyzing
Block #106,100,077
9 transactions · 8 stateful · 2026-09-19 06:00:42 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,100,077
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
updateDataFeedsValuesPartial
#5
0x5acec890
#6
setData
#7
execFwdPositionOpsV2
#8
execOrders
#3
0x5acec890
· blocks 1
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e451306…7993
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b1
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b2
0x37db7f…ec7b
4 touches
1 conflict
0x9d73941a…4ddf
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x143dba04…1b98
0x37db7f…ec7b
4 touches
1 conflict
0xef17b8cd…9511
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
0x1e451306ff…fa7993
Audit this contract →
← previous block
·
next block →
recent activity