pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,758,794
← previous block
next block →
recent activity
Analyzing
Block #74,758,794
10 transactions · 9 stateful · 2026-05-15 13:16:56 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,758,794
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
updatePrices
#3
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x39435dac
#8
setData
#9
0x39435dac
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ddd70a9…4e26
0x34b655…2a6f
4 touches
1 conflict
0x10814d14…cdda
0x34b655…2a6f
4 touches
1 conflict
0x28f3d23f…9bc6
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xb7960be3…7f19
0x34b655…2a6f
4 touches
1 conflict
0xdbdf1d70…6c25
0x34b655…2a6f
4 touches
1 conflict
0xeb0b1d43…9559
0x34b655…2a6f
4 touches
1 conflict
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
0x0ddd70a9dd…124e26
Audit this contract →
← previous block
·
next block →
recent activity