pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,454,317
← previous block
next block →
recent activity
Analyzing
Block #87,454,317
9 transactions · 7 stateful · 2026-07-13 09:05:22 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,454,317
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
forward
#6
approve
#7
setData
#8
0xc7e3ec2c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xd7e9e97b…8d1e
0x34b655…2a6f
4 touches
1 conflict
0xe6b02948…7274
0x34b655…2a6f
4 touches
1 conflict
0x43187d81…281b
0x34b655…2a6f
2 touches
0 conflicts
0x43187d81…281c
0x34b655…2a6f
2 touches
0 conflicts
0x47fe7a68…e7c8
0x34b655…2a6f
2 touches
0 conflicts
0x5b9e5ecc…2bc7
0x34b655…2a6f
2 touches
0 conflicts
0x5e4a329f…bc40
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