pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,913,034
← previous block
next block →
recent activity
Analyzing
Block #85,913,034
9 transactions · 7 stateful · 2026-07-06 05:24:10 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,913,034
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrder
#3
updateDataFeedsValuesPartial
#4
0x6a4b3c72
· blocks 2
#6
setData
#7
0x1d27a9…25f9
#5
0x6a4b3c72
· blocks 1
#8
0x6a4b3c72
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x40cf21e3…e2c7
0x34b655…2a6f
2 touches
0 conflicts
0x5b17482f…0dc4
0x34b655…2a6f
2 touches
0 conflicts
0xa20f418b…c252
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:
0x681e908b…e1ae09
3 conflicts on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity