pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,142,195
← previous block
next block →
recent activity
Analyzing
Block #85,142,195
12 transactions · 10 stateful · 2026-07-02 15:49:34 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,142,195
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execute
#5
0x3f5c179b
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
forward
#10
setData
#9
0xed82b078
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x305e6edb…89b1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x264f7d7d…8444
0x34b655…2a6f
3 touches
1 conflict
0x00585ef7…dd7c
0x34b655…2a6f
2 touches
0 conflicts
0x03a55247…abfe
0x34b655…2a6f
2 touches
0 conflicts
0x043488e6…2455
0x34b655…2a6f
2 touches
0 conflicts
0x0ce68d9a…3aa5
0x34b655…2a6f
2 touches
0 conflicts
0x0eedf48e…ab41
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
0x305e6edb9c…d189b1
Audit this contract →
← previous block
·
next block →
recent activity