pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,571,509
← previous block
next block →
recent activity
Analyzing
Block #84,571,509
9 transactions · 7 stateful · 2026-06-30 00:23:03 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,571,509
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
execOrders
· blocks 2
#4
execFwdPositionOps
#6
0x6a430cdf
#7
setData
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x744e0a36…70f7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x801058a8…5bc3
0x34b655…2a6f
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
2 touches
0 conflicts
0x1c3b9790…3f52
0x34b655…2a6f
2 touches
0 conflicts
0x24be6934…997d
0x34b655…2a6f
2 touches
0 conflicts
0x2b111712…0e59
0x34b655…2a6f
2 touches
0 conflicts
0x2ffc4fb0…3a78
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
0x744e0a3655…6d70f7
Audit this contract →
← previous block
·
next block →
recent activity