pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,347,128
← previous block
next block →
recent activity
Analyzing
Block #84,347,128
11 transactions · 9 stateful · 2026-06-28 23:26:25 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,347,128
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
execute
#4
execFwdPositionOps
· blocks 1
#5
forward
#6
execFwdPositionOps
#8
0x64480813
#9
setData
#10
0xa5f613…35fd
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03e24373…2d95
0x01bff4…1071
2 touches
0 conflicts
0x28749d68…553d
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
0x6f132c01d5…7dcdcd
Audit this contract →
← previous block
·
next block →
recent activity