pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,643,863
← previous block
next block →
recent activity
Analyzing
Block #85,643,863
12 transactions · 11 stateful · 2026-07-04 23:30:19 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,643,863
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
0x38ae9ef8
· blocks 1
#5
execFwdPositionOps
#7
forward
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
execOrders
#4
0x8f9ad8be
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b416
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x46b62326…9b3c
0xa6afd3…d132
4 touches
1 conflict
0xa19aba84…8922
0xa6afd3…d132
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
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:
0x928dc8af…fd8207
1 conflict on slot
0x6ede85f4f8…2e0b8b
Audit this contract →
← previous block
·
next block →
recent activity