pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,423,687
← previous block
next block →
recent activity
Analyzing
Block #91,423,687
13 transactions · 10 stateful · 2026-07-29 19:10:50 UTC
Parallelism
69
/100
Blocked
30
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,423,687
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updatePrices
· blocks 3
#6
updatePrices
#8
execOrders
#9
0xed82b078
#10
updateDataFeedsValuesPartial
#11
setData
#12
0x59558d29
#4
updatePrices
· blocks 2
#5
updatePrices
· blocks 1
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x002f8e6f…ecab
0x34b655…2a6f
2 touches
0 conflicts
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
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:
0x48cba278…e2b48b
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity