pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,415,846
← previous block
next block →
recent activity
Analyzing
Block #74,415,846
9 transactions · 8 stateful · 2026-05-13 23:04:07 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,415,846
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xed82b078
· blocks 1
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
closeTrade
#7
setData
#8
0x39435dac
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x250fa399…7d69
0x065c9d…c394
3 touches
1 conflict
0xa76195da…9ad1
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x31b60059…7900
0x002560…1a4f
2 touches
0 conflicts
0x40ac22bb…a49b
0x002560…1a4f
2 touches
0 conflicts
0xe74d8286…be05
0x002560…1a4f
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
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:
0x065c9d28…a9c394
1 conflict on slot
0x250fa39910…c77d69
Audit this contract →
← previous block
·
next block →
recent activity