pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,454,369
← previous block
next block →
recent activity
Analyzing
Block #87,454,369
9 transactions · 6 stateful · 2026-07-13 09:05:43 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,454,369
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x39435dac
#6
0x23afbff3
#7
0x6a54aadf
#8
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4faeec21…da80
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xac388ba5…a800
0x34b655…2a6f
4 touches
1 conflict
0xbbae5d58…a956
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xd7e9e97b…8d1e
0x34b655…2a6f
4 touches
1 conflict
0x107c8952…6ea4
0x34b655…2a6f
2 touches
0 conflicts
0x111aafe7…1c41
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
0x4faeec21d1…55da80
Audit this contract →
← previous block
·
next block →
recent activity