pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#72,972,715
← previous block
next block →
recent activity
Analyzing
Block #72,972,715
11 transactions · 8 stateful · 2026-05-07 06:42:53 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,972,715
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xc431bdc8
#3
approve
#4
batchUpdate
· blocks 1
#6
0xeffdedb0
#7
setData
#8
0x4470a5…ee7e
#9
execOrders
· blocks 1
#5
batchUpdate
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3927a50…afa7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3b8ffd61…f3ad
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x969ade23…b96e
0x065c9d…c394
2 touches
0 conflicts
0xd65bb619…8762
0x065c9d…c394
2 touches
0 conflicts
0xf73df2a8…119c
0x065c9d…c394
2 touches
0 conflicts
0x64461c10…e86d
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
0xc3927a502e…f8afa7
Audit this contract →
← previous block
·
next block →
recent activity