pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,410,041
← previous block
next block →
recent activity
Analyzing
Block #74,410,041
12 transactions · 9 stateful · 2026-05-13 22:25:34 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,410,041
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
redeemDelegations
#4
0x5339c59f
#5
0x6a04fad5
#6
setData
#7
0x0d5253…3827
#8
0xdfc1e3…5ea6
#9
0xc0053a…4595
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03953790…2fc3
0x065c9d…c394
2 touches
0 conflicts
0xe07093ff…f8d6
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x5fad6fee64…277714
Audit this contract →
← previous block
·
next block →
recent activity