pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,342,689
← previous block
next block →
recent activity
Analyzing
Block #74,342,689
9 transactions · 8 stateful · 2026-05-13 14:57:17 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,342,689
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x98717539
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a0491c4
#8
setData
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x904fc3c0…00ec
0x34b655…2a6f
4 touches
1 conflict
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x652acceb…1651
0x34b655…2a6f
2 touches
0 conflicts
0x694b052d…3904
0x34b655…2a6f
2 touches
0 conflicts
0xa3ff1ab2…8ae3
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:
Perpl
1 conflict on slot
0xfa2527aaf5…479dd5
Audit this contract →
← previous block
·
next block →
recent activity