pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,417,464
← previous block
next block →
recent activity
Analyzing
Block #91,417,464
13 transactions · 10 stateful · 2026-07-29 18:39:30 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,417,464
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
aggregate3
#8
0x0f6795d9
· blocks 1
#10
forward
#11
0x39435dac
#12
setData
#3
updatePrices
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0d4ff179…5538
0x34b655…2a6f
2 touches
0 conflicts
0x0e383049…d572
0x34b655…2a6f
2 touches
0 conflicts
0x1643e0fb…7385
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
0xf9e23360ff…e88ef7
Audit this contract →
← previous block
·
next block →
recent activity