pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,328,994
← previous block
next block →
recent activity
Analyzing
Block #71,328,994
11 transactions · 9 stateful · 2026-04-29 16:03:17 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
#71,328,994
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
#5
claim
#6
setData
#7
execOrders
#8
updatePrices
· blocks 1
#9
updatePrices
#10
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0d65fa46…8a24
0x065c9d…c394
2 touches
0 conflicts
0x21c73bfa…7648
0x065c9d…c394
2 touches
0 conflicts
0xb1cac00a…4804
0x065c9d…c394
2 touches
0 conflicts
0xb2ae3c3b…f910
0x065c9d…c394
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:
0xc1a5781e…c78e1a
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity