pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,782,824
← previous block
next block →
recent activity
Analyzing
Block #74,782,824
7 transactions · 6 stateful · 2026-05-15 15:57:47 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,782,824
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
addLiquidity
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#3
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x50033f98…ea79
0x065c9d…c394
2 touches
1 conflict
0xdda5f088…704d
0x065c9d…c394
2 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c5395f6…a6eb
0x065c9d…c394
2 touches
0 conflicts
0x8f8fac2a…1a10
0x065c9d…c394
2 touches
0 conflicts
0xec5f0096…d093
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity