pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,396,469
← previous block
next block →
recent activity
Analyzing
Block #91,396,469
11 transactions · 8 stateful · 2026-07-29 16:53:30 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,396,469
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x57368ddf
#6
0xc925b3a5
#7
0x6a6a3082
#8
0x39435dac
#9
setData
#10
0xc7e3ec2c
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x157b951c…9b2e
0x34b655…2a6f
2 touches
0 conflicts
0x438268c2…c848
0x34b655…2a6f
2 touches
0 conflicts
0x438268c2…c849
0x34b655…2a6f
2 touches
0 conflicts
0x5fde4971…aac9
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
0x5b6af0070f…160f35
Audit this contract →
← previous block
·
next block →
recent activity