pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,348,809
← previous block
next block →
recent activity
Analyzing
Block #86,348,809
13 transactions · 11 stateful · 2026-07-08 05:53:20 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,348,809
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
updateDataFeedsValuesPartial
#3
0x0c7abd22
#4
0x57368ddf
#5
batchUpdate
#6
updateDataFeedsValuesPartial
#7
0x6a4de648
#8
transfer
#9
setData
#10
execOrders
· blocks 1
#12
0xc7e3ec2c
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x470038e2…609b
0x065c9d…c394
2 touches
0 conflicts
0x65f5dd29…f426
0x065c9d…c394
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity