pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,790,308
← previous block
next block →
recent activity
Analyzing
Block #86,790,308
14 transactions · 8 stateful · 2026-07-10 07:05:54 UTC
Parallelism
86
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,790,308
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x13572d0b
#2
0x0c7abd22
#3
0xcf7468f4
#4
0x1094dc9f
· blocks 1
#5
0xab083028
#6
execOrder
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#10
execFwdPositionOps
#11
execFwdPositionOps
#12
setData
#13
0xc0e6bb…e76c
#9
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x398e3d…298c
4 touches
1 conflict
0x00000000…0002
0x398e3d…298c
4 touches
1 conflict
0x00000000…0004
0x398e3d…298c
4 touches
1 conflict
0x00000000…000c
0x398e3d…298c
4 touches
1 conflict
0x9ef62133…9b47
0x3bd359…433a
4 touches
1 conflict
0xf6802cf0…344f
0x000000…012a
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a995
0x188d58…ea8e
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:
0x398e3d74…e2298c
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity