pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,331,910
← previous block
next block →
recent activity
Analyzing
Block #86,331,910
12 transactions · 10 stateful · 2026-07-08 04:00:32 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,331,910
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
· blocks 1
#2
execOrders
#3
execOrders
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0xed82b078
#8
execFwdPositionOps
#9
forward
#10
updateDataFeedsValuesPartial
#11
setData
#4
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe90b7bce…c2e0
0xfa32f9…f3f0
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x38b5b2ce…c5bb
0x2d82ac…5fd8
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0xf9da5665…2703
0x754704…b603
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:
0xfa32f9ec…fef3f0
1 conflict on slot
0xe90b7bceb6…a7c2e0
Audit this contract →
← previous block
·
next block →
recent activity