pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,594,164
← previous block
next block →
recent activity
Analyzing
Block #85,594,164
8 transactions · 6 stateful · 2026-07-04 17:59:31 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,594,164
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
· blocks 1
#4
0x6a494a7b
#5
setData
#6
execOrders
#7
execOrders
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x211c1377…616e
0x34b655…2a6f
2 touches
0 conflicts
0x38a6ef6a…4fee
0x34b655…2a6f
2 touches
0 conflicts
0x427d1120…4eb1
0x34b655…2a6f
2 touches
0 conflicts
0x4b9462c4…0fef
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
1 conflict on slot
0x85eb131679…60bb9e
Audit this contract →
← previous block
·
next block →
recent activity