pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,690,035
← previous block
next block →
recent activity
Analyzing
Block #87,690,035
9 transactions · 9 stateful · 2026-07-14 11:22:16 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,690,035
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#7
setData
#8
0x39435dac
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf6de35e…bafd
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x16a1aa97…5c89
0x34b655…2a6f
2 touches
0 conflicts
0x177f8c24…a64d
0x34b655…2a6f
2 touches
0 conflicts
0x22c17b4e…e07e
0x34b655…2a6f
2 touches
0 conflicts
0x22c17b4e…e07f
0x34b655…2a6f
2 touches
0 conflicts
0x3531ea1c…d294
0x34b655…2a6f
2 touches
0 conflicts
0x40080907…45cc
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:
Perpl
1 conflict on slot
0xbf6de35e01…bfbafd
Audit this contract →
← previous block
·
next block →
recent activity