pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,355,042
← previous block
next block →
recent activity
Analyzing
Block #74,355,042
12 transactions · 11 stateful · 2026-05-13 16:19:24 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,355,042
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x98717539
· blocks 1
#7
0x98717539
#8
approve
#9
cancel
#10
0x6a04a503
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x84165488…ad52
0x065c9d…c394
2 touches
0 conflicts
0xce9294fa…c21d
0x065c9d…c394
2 touches
0 conflicts
0xf39a2374…f37a
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
2 touches
0 conflicts
0x76e559a4…77fb
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:
0x34b6552d…112a6f
1 conflict on slot
0x8c49c85c3e…afee96
Audit this contract →
← previous block
·
next block →
recent activity