pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,915,422
← previous block
next block →
recent activity
Analyzing
Block #74,915,422
9 transactions · 9 stateful · 2026-05-16 06:42:12 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,915,422
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
permit2TransferAndMulticall
· blocks 1
#3
forward
#4
updateDataFeedsValuesPartial
#6
setData
#7
0x6a08123b
#8
0x39435dac
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x175e21b3…a4f5
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x16582ecc…a3ae
0x065c9d…c394
2 touches
0 conflicts
0x2dde8967…ecab
0x065c9d…c394
2 touches
0 conflicts
0x93f91e01…22cc
0x065c9d…c394
2 touches
0 conflicts
0xb48e72d7…3bc1
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:
0x065c9d28…a9c394
1 conflict on slot
0x348fda08cf…fc7e96
Audit this contract →
← previous block
·
next block →
recent activity