pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,281,513
← previous block
next block →
recent activity
Analyzing
Block #74,281,513
6 transactions · 5 stateful · 2026-05-13 08:10:18 UTC
Parallelism
67
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,281,513
· 6 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#4
0x6a043262
#5
setData
#3
0x5339c59f
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
0x52d94a5e…d39a
0x065c9d…c394
4 touches
1 conflict
0xed27ed21…0552
0x065c9d…c394
3 touches
1 conflict
0x00d98585…1705
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x366c7848…6634
0x065c9d…c394
2 touches
0 conflicts
0x5a23814e…b484
0x065c9d…c394
2 touches
0 conflicts
0x7613eaeb…7bb6
0x065c9d…c394
2 touches
0 conflicts
0xb72fc59a…5a21
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x52d94a5e55…e3d39a
Audit this contract →
← previous block
·
next block →
recent activity