pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,483,786
← previous block
next block →
recent activity
Analyzing
Block #86,483,786
11 transactions · 10 stateful · 2026-07-08 20:55:34 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,483,786
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execOrders
· blocks 1
#5
0x6a4eb9bd
#6
0x5a5d9a99
#7
0x3f5c179b
#8
setData
#9
0xd99db1…3730
#10
execOrders
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0xfc8f5c32…c8fb
0x34b655…2a6f
4 touches
1 conflict
0x01c969a3…227b
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x451f5977…7300
0x34b655…2a6f
4 touches
1 conflict
0x572f121e…964f
0x34b655…2a6f
4 touches
1 conflict
0x69ca0810…e942
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xc948dbdcb8…f4199a
Audit this contract →
← previous block
·
next block →
recent activity