pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,416,087
← previous block
next block →
recent activity
Analyzing
Block #73,416,087
12 transactions · 11 stateful · 2026-05-09 07:53:00 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,416,087
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69fee854
#2
updatePrices
#3
execOrders
#4
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x323fe4ce
#7
updateDataFeedsValuesPartial
#8
exactInputSingle
#9
0xeffdedb0
#10
setData
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0x273d80cd…9ecc
0x34b655…2a6f
4 touches
1 conflict
0xcfdbe862…6b0e
0x34b655…2a6f
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x23951077…539b
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
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
0x6eba5e7f6a…ac4b52
Audit this contract →
← previous block
·
next block →
recent activity