pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,637,758
← previous block
next block →
recent activity
Analyzing
Block #74,637,758
12 transactions · 11 stateful · 2026-05-14 23:49:05 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,637,758
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
depositNative
#2
modifyLiquidities
#3
0xed82b078
· blocks 1
#4
updatePrices
· blocks 1
#6
aggregate3
#7
updateDataFeedsValuesPartial
#9
0x5339c59f
#10
approve
#11
setData
#5
updatePrices
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01110bdc…ff28
0x065c9d…c394
2 touches
0 conflicts
0x563dc182…3fb5
0x188d58…ea8e
2 touches
0 conflicts
0x563dc182…3fb6
0x188d58…ea8e
2 touches
0 conflicts
0x8fe8bbd4…f33f
0x21e325…7777
2 touches
0 conflicts
0xd06cc746…27e4
0x21e325…7777
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
0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block
·
next block →
recent activity