pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,889,550
← previous block
next block →
recent activity
Analyzing
Block #90,889,550
9 transactions · 9 stateful · 2026-07-27 22:21:24 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,889,550
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
0x6a67da5c
#8
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x10f8501f…7831
0x34b655…2a6f
2 touches
0 conflicts
0x3b7c02f2…91de
0x3bd359…433a
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0xc7ea2751…3347
0x3bd359…433a
2 touches
0 conflicts
0x40fd70b1…7250
0x754704…b603
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
0x8743e1bab8…0a8331
Audit this contract →
← previous block
·
next block →
recent activity