pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,221,261
← previous block
next block →
recent activity
Analyzing
Block #90,221,261
10 transactions · 9 stateful · 2026-07-25 14:04:17 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,221,261
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
· blocks 1
#3
0x36f359b0
#4
0x39435dac
· blocks 1
#6
0x39435dac
#7
0x6a64c2d9
#8
setData
#9
0x39435dac
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x7491ef1e…2478
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
2 touches
0 conflicts
0x1d1b6d85…3e2e
0x34b655…2a6f
2 touches
0 conflicts
0x296231a8…d4f4
0x34b655…2a6f
2 touches
0 conflicts
0x5110a94f…86d1
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity