pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,298,066
← previous block
next block →
recent activity
Analyzing
Block #74,298,066
10 transactions · 9 stateful · 2026-05-13 10:00:30 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,298,066
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
transfer
· blocks 2
#5
0x1ffa3c9b
#6
updateDataFeedsValuesPartial
#7
0x98717539
#8
0x6a044c36
#9
setData
#3
transfer
· blocks 1
#4
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e24c5e6…330d
0x754704…b603
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2182cfdf…4ff4
0x065c9d…c394
2 touches
0 conflicts
0x2ad0da09…ab4c
0x065c9d…c394
2 touches
0 conflicts
0x52af583d…2bc7
0x065c9d…c394
2 touches
0 conflicts
0xc13348e5…0264
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:
0x754704bc…afb603
3 conflicts on slot
0x5e24c5e63c…91330d
Audit this contract →
← previous block
·
next block →
recent activity