pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,231,074
← previous block
next block →
recent activity
Analyzing
Block #112,231,074
10 transactions · 10 stateful · 2026-10-10 16:33:15 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#112,231,074
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x32d01e04
#2
0x59558d29
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
aggregate3Value
#6
execFwdPositionOpsV2
· blocks 1
#8
0x61d59c2d
· blocks 1
#7
execFwdPositionOpsV2
#9
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x822abf1b…c628
0x508254…98bd
4 touches
1 conflict
0x822abf1b…c63f
0x508254…98bd
4 touches
1 conflict
0x822abf1b…c65d
0x508254…98bd
4 touches
1 conflict
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360c
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360d
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:
0x508254c8…4a98bd
1 conflict on slot
0x822abf1b79…5ec628
Audit this contract →
← previous block
·
next block →
recent activity