pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,865,716
← previous block
next block →
recent activity
Analyzing
Block #90,865,716
10 transactions · 7 stateful · 2026-07-27 20:21:30 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,865,716
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xfb63f1…ad31
#2
0x289404…2be5
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
executeBatch
#8
0x6a67be42
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc44810d5…a00a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ffbc5c9…461f
0x34b655…2a6f
2 touches
0 conflicts
0x278a4c97…dfcf
0x34b655…2a6f
2 touches
0 conflicts
0x2b747f7d…4d32
0x34b655…2a6f
2 touches
0 conflicts
0x2f059586…7d22
0x34b655…2a6f
2 touches
0 conflicts
0x34731dbd…e467
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
0xc44810d5f6…d2a00a
Audit this contract →
← previous block
·
next block →
recent activity