pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,691,127
← previous block
next block →
recent activity
Analyzing
Block #87,691,127
13 transactions · 12 stateful · 2026-07-14 11:29:33 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,691,127
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
#7
updatePosition
#8
0xc925b3a5
· blocks 1
#10
batchUpdate
#11
0x6a561e15
#12
setData
#9
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0bead444…5793
0x34b655…2a6f
2 touches
0 conflicts
0x15bb0662…b802
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfa032…139c
0x34b655…2a6f
2 touches
0 conflicts
0x38948e75…437a
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:
USDC (USDC)
1 conflict on slot
0x55b4e430de…d044cb
Audit this contract →
← previous block
·
next block →
recent activity