pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,789,600
← previous block
next block →
recent activity
Analyzing
Block #74,789,600
14 transactions · 11 stateful · 2026-05-15 16:43:03 UTC
Parallelism
79
/100
Blocked
18
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,789,600
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updatePrices
#5
0x0c7abd22
#6
addLiquidity
#7
multicall
#8
0x1a945f9c
#9
execOrders
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
setData
#13
0x42dd8743
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x064a3cb8…c43e
0x09475a…400f
2 touches
0 conflicts
0x13420bae…919f
0x09475a…400f
2 touches
0 conflicts
0xd420023a…cf6a
0x09475a…400f
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x96a64838…2469
0x5afd3e…7620
2 touches
0 conflicts
0xad02aa4a…ed6d
0x5afd3e…7620
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