pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,369,163
← previous block
next block →
recent activity
Analyzing
Block #74,369,163
11 transactions · 8 stateful · 2026-05-13 17:53:20 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,369,163
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x58ea52…47ca
#2
0x1ffa3c9b
#3
updatePrices
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#7
closeTrade
#8
transfer
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x40ecd90c…10ed
0x065c9d…c394
2 touches
0 conflicts
0x66d18879…a6d4
0x065c9d…c394
2 touches
0 conflicts
0x6eee9f9e…2c25
0x065c9d…c394
2 touches
0 conflicts
0x85ea96a2…251c
0x065c9d…c394
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:
0x34b6552d…112a6f
1 conflict on slot
0x070a562acf…648147
Audit this contract →
← previous block
·
next block →
recent activity