pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#73,216,176
← previous block
next block →
recent activity
Analyzing
Block #73,216,176
14 transactions · 12 stateful · 2026-05-08 09:42:54 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,216,176
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x69fdb096
#3
exactInputSingle
#4
execute
#5
updatePrices
#6
execOrders
· blocks 1
#7
0x1a945f9c
#8
updateDataFeedsValuesPartial
#9
setData
#10
forward
#11
0x69fdb096
#12
0xeffdedb0
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaca243a…f9de
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0xb55d56f9…082f
0x065c9d…c394
2 touches
0 conflicts
0xbd7e37a9…9eb5
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:
Perpl
1 conflict on slot
0xdaca243a5e…09f9de
Audit this contract →
← previous block
·
next block →
recent activity