pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,336,307
← previous block
next block →
recent activity
Analyzing
Block #74,336,307
13 transactions · 9 stateful · 2026-05-13 14:14:49 UTC
Parallelism
69
/100
Blocked
33
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,336,307
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x39ecce49
#2
updatePrices
· blocks 3
#6
0x5bf9264c
#7
0x5bf9264c
#8
updateDataFeedsValuesPartial
#9
0x6a0487d1
#10
setData
#11
0xc3d79a…06bc
#12
0x39435dac
#3
updatePrices
· blocks 2
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x139aab…382b
2 touches
0 conflicts
0x00000000…0001
0x139aab…382b
2 touches
0 conflicts
0x00000000…0003
0x139aab…382b
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity