pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,748,862
← previous block
next block →
recent activity
Analyzing
Block #120,748,862
10 transactions · 10 stateful · 2026-11-09 12:21:19 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,748,862
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
setData
#2
execOrders
· blocks 1
#4
0x59558d29
#5
0x35e534ea
#6
execOrders
· blocks 2
#9
transferWithAuthorization
#3
execOrders
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x100812e9…12b7
0x34b655…2a6f
6 touches
3 conflicts
0xc39ff265…485e
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0xe226a0be…c046
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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
3 conflicts on slot
0x100812e99b…9e12b7
Audit this contract →
← previous block
·
next block →
recent activity