pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,627,274
← previous block
next block →
recent activity
Analyzing
Block #86,627,274
9 transactions · 8 stateful · 2026-07-09 12:55:52 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,627,274
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
0xab083028
#3
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
setData
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
2 touches
0 conflicts
0x06fca7ed…67f8
0x43cf54…7777
2 touches
0 conflicts
0x0db0aaac…e94d
0x43cf54…7777
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:
0xb1dbf05f…b1c0d3
1 conflict on slot
0x6c68ddc9e3…b0d106
Audit this contract →
← previous block
·
next block →
recent activity