pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,468,112
← previous block
next block →
recent activity
Analyzing
Block #74,468,112
16 transactions · 9 stateful · 2026-05-14 04:52:03 UTC
Parallelism
88
/100
Blocked
22
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,468,112
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
0x366fe5db
#10
multicall
#11
forward
#12
setData
#13
0x1bb71f…ca29
#14
0xc05bdd…ae52
#15
0xdfd955…bbaa
#2
swap
#4
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
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xfeca1573…d30c
0x1fb933…7777
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x67d846dd…358c
0x1fb933…7777
2 touches
0 conflicts
0x754493a0…e69b
0x3bd359…433a
2 touches
0 conflicts
0x0d51d107…eb3e
0x91b81b…6d56
2 touches
0 conflicts
0x7408c11b…7dd5
0x91b81b…6d56
2 touches
0 conflicts
0x82d396a1…2adb
0x91b81b…6d56
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity