pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,441,033
← previous block
next block →
recent activity
Analyzing
Block #74,441,033
14 transactions · 12 stateful · 2026-05-14 01:51:49 UTC
Parallelism
71
/100
Blocked
25
%
Avg conflicts / tx
0.43
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,441,033
· 14 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
· blocks 3
#6
get_block_hash_257335279069929
#7
multicall
#8
updateDataFeedsValuesPartial
#9
setData
#10
redeemDelegations
#11
updatePosition
#12
deposit
#13
0x6a052b2d
#3
updatePrices
· blocks 2
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
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
0xc1d2d0e5…3299
0x09475a…400f
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1dafb7f2…0306
0xa6b615…8e35
2 touches
0 conflicts
0x00000000…000b
0xbeef04…ef42
2 touches
0 conflicts
0x00000000…000f
0xbeef04…ef42
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