pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,500,400
← previous block
next block →
recent activity
Analyzing
Block #73,500,400
13 transactions · 11 stateful · 2026-05-09 17:14:03 UTC
Parallelism
69
/100
Blocked
27
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,500,400
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x69ff6bd3
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
· blocks 3
#8
0x39435dac
#9
0x98717539
#10
0x69ff6bd2
#11
setData
#12
0x39435dac
#5
updatePrices
· blocks 2
#6
updatePrices
· blocks 1
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f41c833…9c38
0x34b655…2a6f
2 touches
0 conflicts
0x693d979a…f2bd
0x34b655…2a6f
2 touches
0 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
2 touches
0 conflicts
0xb81d3ee7…3947
0x34b655…2a6f
2 touches
0 conflicts
0xbd242b8a…897b
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:
0xab35264b…1cfa38
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity