pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#118,535,158
← previous block
next block →
recent activity
Analyzing
Block #118,535,158
10 transactions · 9 stateful · 2026-11-01 17:56:44 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#118,535,158
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
0x59558d29
#3
0x35e534ea
#4
0x35e534ea
#5
0x35e534ea
#6
0x5acec890
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#8
execFwdPositionOpsV2
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
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x25ebe5e6…1791
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x816d0352…a531
0x581b9a…b67b
2 touches
0 conflicts
0x78aed805…ed00
0xed3727…f3af
2 touches
0 conflicts
0x78aed805…ed01
0xed3727…f3af
2 touches
0 conflicts
0x78aed805…ed02
0xed3727…f3af
2 touches
0 conflicts
0x8d2cea17…1580
0xed3727…f3af
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity