pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,058,178
← previous block
next block →
recent activity
Analyzing
Block #86,058,178
10 transactions · 9 stateful · 2026-07-06 21:33:05 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,058,178
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 3
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#6
0x6a4c1f89
#7
setData
#9
0xc7e3ec2c
#2
execOrders
· blocks 1
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa20a130c…5d59
0x34b655…2a6f
6 touches
3 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0xa0002c18…c480
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb274cb13…808b
0x34b655…2a6f
3 touches
1 conflict
0x3a7fb5b5…f0e5
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
3 conflicts on slot
0xa20a130ca6…b85d59
Audit this contract →
← previous block
·
next block →
recent activity