pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,951,497
← previous block
next block →
recent activity
Analyzing
Block #74,951,497
15 transactions · 11 stateful · 2026-05-16 10:43:28 UTC
Parallelism
87
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,951,497
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0x98717539
#4
updatePosition
#5
closeTrade
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x6a084ac8
#10
0x46171b…564b
#11
0xe9f501…2c78
#12
setData
#13
claim
#14
exactInputSingle
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe15363…9a92
0x3ec731…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3914b736…9377
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x8404070b…464d
0x34b655…2a6f
2 touches
0 conflicts
0x8aa1941d…2988
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:
0x3ec73109…ff7777
1 conflict on slot
0x6fe1536325…7c9a92
Audit this contract →
← previous block
·
next block →
recent activity