pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,236,103
← previous block
next block →
recent activity
Analyzing
Block #112,236,103
11 transactions · 10 stateful · 2026-10-10 16:58:33 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,236,103
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x32d01e04
#3
0xdab852…6f90
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
#7
0x84403c1b
· blocks 1
#9
execFwdPositionOpsV2
#10
setData
#8
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x227ca763…69bd
0x34b655…2a6f
4 touches
1 conflict
0x27145bc1…96cc
0x34b655…2a6f
4 touches
1 conflict
0x93d22891…e30d
0x34b655…2a6f
4 touches
1 conflict
0x98834cc0…6c23
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
2 touches
0 conflicts
0x00000000…004c
0x80c745…7210
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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:
Perpl
1 conflict on slot
0x227ca7634c…3a69bd
Audit this contract →
← previous block
·
next block →
recent activity