pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,417,833
← previous block
next block →
recent activity
Analyzing
Block #73,417,833
15 transactions · 11 stateful · 2026-05-09 08:04:41 UTC
Parallelism
87
/100
Blocked
18
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,417,833
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69feeb11
#2
exactOutputSingle
#3
updatePrices
· blocks 1
#5
aggregate3
#6
0xed82b078
· blocks 1
#7
0xed82b078
#8
0xed82b078
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
setData
#13
0x34653439
#14
0x39435dac
#4
updatePrices
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x23035f…7992
2 touches
0 conflicts
0xb1acfe51…c6b1
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x418541…9c3d
2 touches
0 conflicts
0x00000000…0004
0x43a05b…a68f
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity