pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,447,048
← previous block
next block →
recent activity
Analyzing
Block #86,447,048
8 transactions · 5 stateful · 2026-07-08 16:49:41 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,447,048
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
forward
#5
setData
#6
0x331c86…221a
#7
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e9f111c…0869
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xc8a83bd5…5b5e
0x34b655…2a6f
3 touches
1 conflict
0x0a6551a9…e6f3
0x34b655…2a6f
2 touches
0 conflicts
0x38737e9b…8374
0x34b655…2a6f
2 touches
0 conflicts
0x5571e830…9cea
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x62f9317e…9e32
0x34b655…2a6f
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
0x0e9f111c42…6a0869
Audit this contract →
← previous block
·
next block →
recent activity