pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,348,709
← previous block
next block →
recent activity
Analyzing
Block #86,348,709
9 transactions · 8 stateful · 2026-07-08 05:52:40 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,348,709
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x938bf18e
#8
0xc7e3ec2c
#2
0xab083028
· blocks 1
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0d4d5…e5aa
0x065c9d…c394
2 touches
0 conflicts
0x2dafe968…e4d6
0x065c9d…c394
2 touches
0 conflicts
0x733f3b14…0047
0x065c9d…c394
2 touches
0 conflicts
0xadb10ccb…cae0
0x065c9d…c394
2 touches
0 conflicts
0x0f8965bb…e238
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xcc8faac238…88c766
Audit this contract →
← previous block
·
next block →
recent activity