pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,049,619
← previous block
next block →
recent activity
Analyzing
Block #87,049,619
14 transactions · 12 stateful · 2026-07-11 11:59:13 UTC
Parallelism
79
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,049,619
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
0x6ad2e98b
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0xc5a04723
#8
forward
#9
execFwdPositionOps
#10
setData
#11
execOrders
· blocks 1
#12
execOrders
· blocks 1
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
13
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2bf7bfa…d195
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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
0xa2bf7bfafc…27d195
Audit this contract →
← previous block
·
next block →
recent activity