pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,986,569
← previous block
next block →
recent activity
Analyzing
Block #74,986,569
10 transactions · 9 stateful · 2026-05-16 14:38:45 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,986,569
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
handleOps
· blocks 1
#5
0x6a0881ec
#6
setData
#7
0xa5e8ae…d3aa
#8
0xae238fb5
#9
0x39435dac
#4
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33a26eb2…2df0
0x5ff137…2789
4 touches
1 conflict
0x00000000…000b
0x754704…b603
4 touches
1 conflict
0xd0fdd34f…60c2
0x754704…b603
4 touches
1 conflict
0xe37e7059…4196
0x754704…b603
3 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x4aa4f53b…899f
0x188d58…ea8e
2 touches
0 conflicts
0x4aa4f53b…89a1
0x188d58…ea8e
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:
0x5ff137d4…6d2789
1 conflict on slot
0x33a26eb216…ad2df0
Audit this contract →
← previous block
·
next block →
recent activity