pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,564,458
← previous block
next block →
recent activity
Analyzing
Block #84,564,458
11 transactions · 10 stateful · 2026-06-29 23:36:01 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,564,458
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execOrders
· blocks 2
#7
execFwdPositionOps
#8
executeBatch
#9
setData
#6
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70638c24…1553
0x34b655…2a6f
6 touches
3 conflicts
0x7bc74ef3…0fee
0x34b655…2a6f
6 touches
3 conflicts
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x443d4ecd…741a
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x81635f2c…28d5
0x34b655…2a6f
4 touches
1 conflict
0x86a6e399…369e
0x34b655…2a6f
4 touches
1 conflict
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
0x70638c2476…811553
Audit this contract →
← previous block
·
next block →
recent activity