pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,594,592
← previous block
next block →
recent activity
Analyzing
Block #87,594,592
12 transactions · 10 stateful · 2026-07-14 00:44:19 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,594,592
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
#3
updatePrices
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
· blocks 1
#10
setData
#11
0x833a4f…363e
#9
0x0f6795d9
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
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0a5dbc1e…74cc
0x34b655…2a6f
2 touches
0 conflicts
0x12a92ce8…db54
0x34b655…2a6f
2 touches
0 conflicts
0x176771f9…c1a4
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity