pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,351,953
← previous block
next block →
recent activity
Analyzing
Block #74,351,953
16 transactions · 14 stateful · 2026-05-13 15:58:49 UTC
Parallelism
75
/100
Blocked
21
%
Avg conflicts / tx
0.38
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,351,953
· 16 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
atInversebrah
#2
updatePrices
· blocks 3
#3
updatePrices
#7
updatePrices
#8
0x98717539
#9
forward
#10
0xc5a04723
#11
forward
#12
forward
#13
updateDataFeedsValuesPartial
#14
setData
#15
0x39435dac
#4
updatePrices
· blocks 2
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
6
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
0x9c618f56…e6cf
0x1001ff…1001
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0x00000000…0000
0x276664…5732
2 touches
0 conflicts
0x00000000…0002
0x276664…5732
2 touches
0 conflicts
0x00000000…0004
0x276664…5732
2 touches
0 conflicts
0x0711ec2d…d973
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:
0xab35264b…1cfa38
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity