pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,902,056
← previous block
next block →
recent activity
Analyzing
Block #74,902,056
11 transactions · 9 stateful · 2026-05-16 05:13:05 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,902,056
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a07fd58
#2
updatePrices
#3
redeemDelegations
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x2287c0…ec0c
#7
0xf64e0b…60b3
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x2452bd…bf95
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x4548467b…9058
0x34b655…2a6f
2 touches
0 conflicts
0x7cee1be1…e770
0x34b655…2a6f
2 touches
0 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
2 touches
0 conflicts
0xa92c8763…6d7f
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
0x97b0b2ee68…854666
Audit this contract →
← previous block
·
next block →
recent activity