pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,649,419
← previous block
next block →
recent activity
Analyzing
Block #74,649,419
11 transactions · 10 stateful · 2026-05-15 01:06:40 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,649,419
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
setPrice
#3
setPrice
#4
setPrice
#5
updatePrices
#6
0x5bf9264c
· blocks 1
#8
0x98717539
#9
updateDataFeedsValuesPartial
#10
setData
#7
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0dd69034…aeb1
0x065c9d…c394
2 touches
0 conflicts
0x296b1f42…d42b
0x065c9d…c394
2 touches
0 conflicts
0x6eec41b3…bba7
0x065c9d…c394
2 touches
0 conflicts
0xafcec7d1…686b
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity