pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,299,039
← previous block
next block →
recent activity
Analyzing
Block #86,299,039
10 transactions · 9 stateful · 2026-07-08 00:20:56 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,299,039
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#5
0x57368ddf
#6
batchUpdate
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3b115d7b…33ac
0x2a68ba…90c5
2 touches
0 conflicts
0x4f394483…ff62
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5318
0x34b655…2a6f
2 touches
0 conflicts
0xf91a3f5f…5926
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x1d9867ade5…7b6d9a
Audit this contract →
← previous block
·
next block →
recent activity