pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,494,745
← previous block
next block →
recent activity
Analyzing
Block #86,494,745
12 transactions · 11 stateful · 2026-07-08 22:08:43 UTC
Parallelism
75
/100
Blocked
18
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,494,745
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
· blocks 2
#3
updateDataFeedsValuesPartial
#4
aggregate3
#5
execFwdPositionOps
#6
forward
#7
execFwdPositionOps
#8
0x6a4ecae3
#9
setData
#11
0xc7e3ec2c
#2
0x98717539
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x3f23cdf6…46a4
0x34b655…2a6f
4 touches
1 conflict
0xda89b873…8516
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x98d58911…19f2
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
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
3 conflicts on slot
0xd99b3b6441…7a1c95
Audit this contract →
← previous block
·
next block →
recent activity