pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,890,051
← previous block
next block →
recent activity
Analyzing
Block #90,890,051
10 transactions · 9 stateful · 2026-07-27 22:23:55 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,890,051
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
forward
#8
0x6a67daf3
#9
setData
#2
0x5a5d9a99
· blocks 1
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93ffcd76…894e
0x34b655…2a6f
4 touches
1 conflict
0x085783c4…ec4d
0x34b655…2a6f
4 touches
1 conflict
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x1282d637…5ff4
0x34b655…2a6f
2 touches
0 conflicts
0x1425201f…3a29
0x34b655…2a6f
2 touches
0 conflicts
0x3dae5ee1…721b
0x34b655…2a6f
2 touches
0 conflicts
0x45ef9175…5ab2
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
0x93ffcd766f…be894e
Audit this contract →
← previous block
·
next block →
recent activity