pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,355,662
← previous block
next block →
recent activity
Analyzing
Block #74,355,662
10 transactions · 10 stateful · 2026-05-13 16:23:31 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,355,662
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
· blocks 1
#3
updatePrices
· blocks 2
#6
updateDataFeedsValuesPartial
#7
0x6a04a5fb
#8
setData
#9
0x39435dac
#2
swap
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x3833ecf1…8134
0xdb8585…7777
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaf7c2ffc…5a6f
0x3bd359…433a
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
2 touches
0 conflicts
0x00000000…0000
0xd004cf…da29
2 touches
0 conflicts
0x00000000…0002
0xd004cf…da29
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
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity