pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,489,687
← previous block
next block →
recent activity
Analyzing
Block #112,489,687
11 transactions · 9 stateful · 2026-10-11 14:14:22 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,489,687
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x59558d29
#3
0x8a5c5f49
#4
execOrders
#5
0x013b6436
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#9
0x61d59c2d
· blocks 1
#10
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c68050…3167
0x508254…98bd
4 touches
1 conflict
0x86c68050…3174
0x508254…98bd
4 touches
1 conflict
0xe70a8ac1…e5e1
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x4ea2b33b…7dbc
0x508254…98bd
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4abaedb1…65b9
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:
0x508254c8…4a98bd
1 conflict on slot
0x86c68050d2…413167
Audit this contract →
← previous block
·
next block →
recent activity