pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,382,933
← previous block
next block →
recent activity
Analyzing
Block #74,382,933
10 transactions · 7 stateful · 2026-05-13 19:25:02 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,382,933
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x6a04d086
#6
0xe9316489
#7
setData
#8
0xb7de35…b688
#9
0x39435dac
#2
exec
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
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x036056…1881
2 touches
0 conflicts
0x357b8726…74c0
0x036056…1881
2 touches
0 conflicts
0x4e1cd3bc…9aff
0x036056…1881
2 touches
0 conflicts
0x00000000…0007
0x09f880…ede0
2 touches
0 conflicts
0x00000000…000a
0x09f880…ede0
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity