pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,108,738
← previous block
next block →
recent activity
Analyzing
Block #120,108,738
14 transactions · 10 stateful · 2026-11-07 06:30:16 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,108,738
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x35e534ea
#3
0x35e534ea
#4
0x5acec890
#5
execOrders
· blocks 1
#6
0x013b6436
#7
redeemDelegations
#8
execFwdPositionOpsV2
#9
setData
#10
exactInputSingle
#12
0x0c7abd22
#13
0x0c7abd22
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x38112ca8…53ec
0x34b655…2a6f
3 touches
1 conflict
0x57bcf8ca…3e5a
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0014
0x80c745…7210
2 touches
0 conflicts
0x00000000…0015
0x80c745…7210
2 touches
0 conflicts
0x00000000…0016
0x80c745…7210
2 touches
0 conflicts
0x00000000…0017
0x80c745…7210
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
0x51fc8795c8…57126f
Audit this contract →
← previous block
·
next block →
recent activity