pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#118,535,137
← previous block
next block →
recent activity
Analyzing
Block #118,535,137
9 transactions · 7 stateful · 2026-11-01 17:56:37 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#118,535,137
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
0x59558d29
#3
execFwdPositionOpsV2
· blocks 1
#5
forward
#6
execFwdPositionOpsV2
#7
publishPrice
#8
setData
#4
execFwdPositionOpsV2
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
0x25ebe5e6…1791
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x276f92ac…5e36
0x264123…670e
2 touches
0 conflicts
0x292f70e5…9943
0x264123…670e
2 touches
0 conflicts
0x8f980e85…4b1a
0x264123…670e
2 touches
0 conflicts
0xad8cee6a…02bb
0x264123…670e
2 touches
0 conflicts
0xb83aa086…05cb
0x264123…670e
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
0x25ebe5e685…af1791
Audit this contract →
← previous block
·
next block →
recent activity