pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,365,270
← previous block
next block →
recent activity
Analyzing
Block #84,365,270
9 transactions · 6 stateful · 2026-06-29 01:27:27 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,365,270
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#4
setData
#5
0xccd88b…749c
#8
0x5d2fd812
#6
execOrders
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d4eb00…30f3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda5e0705…ecb9
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0f8ca43f…83eb
0x34b655…2a6f
2 touches
0 conflicts
0x1041ce1a…fe0f
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
0xd6d4eb00b3…a430f3
Audit this contract →
← previous block
·
next block →
recent activity