pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,578,251
← previous block
next block →
recent activity
Analyzing
Block #87,578,251
9 transactions · 9 stateful · 2026-07-13 22:55:02 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,578,251
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#5
0x0f6795d9
#6
setData
#8
0x3f5c179b
#4
0x0f6795d9
· blocks 1
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcad4d96…c690
0x34b655…2a6f
6 touches
3 conflicts
0x0b277fb8…2d81
0x34b655…2a6f
4 touches
1 conflict
0x0b277fb8…2d82
0x34b655…2a6f
4 touches
1 conflict
0x16dd4651…e88f
0x34b655…2a6f
4 touches
1 conflict
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
0x40f5e9c0…60d5
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x558fd353…1c6b
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xfcad4d96be…a3c690
Audit this contract →
← previous block
·
next block →
recent activity