pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,904,821
← previous block
next block →
recent activity
Analyzing
Block #87,904,821
14 transactions · 14 stateful · 2026-07-15 11:19:21 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,904,821
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
updatePrices
#3
0x5a5d9a99
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
batchUpdate
#8
0x0f6795d9
· blocks 1
#9
0xc5a04723
#11
0x6a576d30
#12
setData
#13
0xc7e3ec2c
#10
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x40287836…2dff
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x3b223675…d6f6
0x111111…db61
2 touches
0 conflicts
0xa93fef74…94b3
0x158622…375e
2 touches
0 conflicts
0x00000000…0000
0x2970fd…1fc2
2 touches
0 conflicts
0x00000000…000a
0x2d8bbb…026a
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity