pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,255,418
← previous block
next block →
recent activity
Analyzing
Block #75,255,418
10 transactions · 8 stateful · 2026-05-17 20:33:24 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,255,418
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
0x98717539
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
0xa391f92f
#7
setData
#8
0x9d177b…c4ee
#9
0x39435dac
#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
0x7c548480…b329
0x42e2ee…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b093160…8a4e
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x32589dde…a20c
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x6ee86c0c…50c6
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:
0x42e2eefe…917777
1 conflict on slot
0x7c5484808b…fdb329
Audit this contract →
← previous block
·
next block →
recent activity