pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,421,054
← previous block
next block →
recent activity
Analyzing
Block #74,421,054
10 transactions · 9 stateful · 2026-05-13 23:38:43 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,421,054
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0xa96df62f
#4
0x98717539
· blocks 1
#5
0x000000b2
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x6a050bfa
#2
updatePrices
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x8b8e4020…11b0
0x34b655…2a6f
2 touches
0 conflicts
0x904fc3c0…00ec
0x34b655…2a6f
2 touches
0 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
2 touches
0 conflicts
0xc5e7b074…3cf3
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity