pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,913,007
← previous block
next block →
recent activity
Analyzing
Block #85,913,007
11 transactions · 9 stateful · 2026-07-06 05:24:00 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,913,007
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x957d4ba0
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
batchUpdate
#6
execFwdPositionOps
#7
setData
#8
0x8fdae4…0784
#9
0xb6a5f5…f35a
#10
0xc7e3ec2c
#2
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x34443913…cbf3
0x336ed4…c59c
2 touches
0 conflicts
0xc88f593e…5d93
0x336ed4…c59c
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:
0x90c3747c…0ebe45
1 conflict on slot
0x0000000000…00000a
Audit this contract →
← previous block
·
next block →
recent activity