pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,542,503
← previous block
next block →
recent activity
Analyzing
Block #90,542,503
6 transactions · 5 stateful · 2026-07-26 17:15:23 UTC
Parallelism
67
/100
Blocked
40
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,542,503
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#4
setData
#3
0x0f6795d9
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x0ec74a3d…432f
0x34b655…2a6f
2 touches
0 conflicts
0x14d0a41d…c614
0x34b655…2a6f
2 touches
0 conflicts
0x16839256…371f
0x34b655…2a6f
2 touches
0 conflicts
0x1bde9f7f…c070
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
0x1a5d321d5d…0da474
Audit this contract →
← previous block
·
next block →
recent activity