pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,404,874
← previous block
next block →
recent activity
Analyzing
Block #74,404,874
9 transactions · 8 stateful · 2026-05-13 21:51:08 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,404,874
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a04f2c4
#2
0xed82b078
· blocks 1
#3
updatePrices
#4
0x1a945f9c
#5
updateDataFeedsValuesPartial
#6
setData
#8
0x39435dac
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc82c6840…a703
0x065c9d…c394
3 touches
1 conflict
0x441a1ad5…855e
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09984f39…b274
0x065c9d…c394
2 touches
0 conflicts
0x9b0d9053…665e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x89301991…902a
0x1efe02…37d6
2 touches
0 conflicts
0xdd0b4c6e…13b4
0x1efe02…37d6
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
0xc82c68400c…29a703
Audit this contract →
← previous block
·
next block →
recent activity