pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,404,286
← previous block
next block →
recent activity
Analyzing
Block #74,404,286
9 transactions · 8 stateful · 2026-05-13 21:47:12 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,286
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
increase
#3
0xc5a04723
#4
updateDataFeedsValuesPartial
#5
0x6a04f1d8
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa486f342…64d5
0x34b655…2a6f
4 touches
1 conflict
0xc684c7fc…0547
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0xa0e22c00…b3b0
0x000000…8ba3
2 touches
0 conflicts
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
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
0xa486f34281…4664d5
Audit this contract →
← previous block
·
next block →
recent activity