pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,515,852
← previous block
next block →
recent activity
Analyzing
Block #90,515,852
13 transactions · 11 stateful · 2026-07-26 15:01:20 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,515,852
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
executeBatch
#3
0x0f6795d9
· blocks 2
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a6621b8
#9
transfer
#10
setData
#11
0x39435dac
#12
0x39435dac
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16eb5040…a048
0x34b655…2a6f
4 touches
1 conflict
0x1960b414…14a6
0x34b655…2a6f
4 touches
1 conflict
0x4253010a…4700
0x34b655…2a6f
4 touches
1 conflict
0x636446ac…f478
0x34b655…2a6f
4 touches
1 conflict
0x636446ac…f479
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x28747f91…a9ff
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
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
0x16eb504010…86a048
Audit this contract →
← previous block
·
next block →
recent activity