pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,409,094
← previous block
next block →
recent activity
Analyzing
Block #91,409,094
12 transactions · 12 stateful · 2026-07-29 17:57:17 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,409,094
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6a6a3f74
#5
handleOps
#6
0x0f6795d9
· blocks 1
#7
relay
#8
0x0f6795d9
#10
setData
#11
0x39435dac
#2
updatePrices
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0f68ef8c…0900
0x000000…a032
2 touches
0 conflicts
0x24a8e790…55e2
0x000000…a032
2 touches
0 conflicts
0x4711c5ea…3b33
0x000000…a032
2 touches
0 conflicts
0x4eb21735…982a
0x000000…a032
2 touches
0 conflicts
0x4fa6e5ed…2e07
0x000000…a032
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity