pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,989,448
← previous block
next block →
recent activity
Analyzing
Block #85,989,448
13 transactions · 11 stateful · 2026-07-06 13:54:02 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,989,448
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a4bb3f1
· blocks 1
#2
execOrders
#3
approve
#4
0x3f5c179b
#5
0x3f5c179b
#6
updateDataFeedsValuesPartial
#8
0x445e1eb7
#9
0xc2af6d…83de
#10
setData
#11
execOrders
#12
0xc7e3ec2c
#7
0x6a4bb3f1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
2 touches
0 conflicts
0x5e438da2…5236
0x34b655…2a6f
2 touches
0 conflicts
0x608ebd53…deda
0x34b655…2a6f
2 touches
0 conflicts
0x75fd2dc7…6997
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity