pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,443,493
← previous block
next block →
recent activity
Analyzing
Block #74,443,493
10 transactions · 8 stateful · 2026-05-14 02:08:12 UTC
Parallelism
80
/100
Blocked
38
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,443,493
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
settle
#4
0x98717539
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x6a052f04
· blocks 1
#2
updatePrices
#5
0x98717539
#9
0x6a052f04
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0xdab59320…142d
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x313f2565…5b00
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:
0xc8689a47…62ee79
1 conflict on slot
0xc6417de023…802191
Audit this contract →
← previous block
·
next block →
recent activity