pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,063,689
← previous block
next block →
recent activity
Analyzing
Block #120,063,689
14 transactions · 14 stateful · 2026-11-07 02:43:11 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,063,689
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6450738f
#2
execOrders
#3
updatePrices
#4
0x35e534ea
#5
0x35e534ea
#6
0x35e534ea
#7
updatePrices
#8
0x5acec890
#9
execPerpOps
· blocks 1
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
setData
#10
execPerpOps
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
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0x276f92ac…5e36
0x264123…670e
2 touches
0 conflicts
0x386ce9fd…caf1
0x264123…670e
2 touches
0 conflicts
0x7003a7a5…94b5
0x264123…670e
2 touches
0 conflicts
0xad8cee6a…02bb
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
0xf5dc501bf7…748313
Audit this contract →
← previous block
·
next block →
recent activity