pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,663,807
← previous block
next block →
recent activity
Analyzing
Block #73,663,807
9 transactions · 8 stateful · 2026-05-10 11:24:12 UTC
Parallelism
44
/100
Blocked
50
%
Avg conflicts / tx
1.11
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,663,807
· 9 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
setData
#4
execute
· blocks 4
#5
execute
· blocks 3
#6
execute
· blocks 2
#7
execute
· blocks 1
#8
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
8
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebc0f21b…5a23
0xf59d81…17a3
10 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0003
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0004
0x63e48b…53f2
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
10 touches
10 conflicts
0xebc0f21b…5a23
0x754704…b603
10 touches
10 conflicts
0x00000000…0000
0x81e8ed…9c15
10 touches
10 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:
0xf59d81cd…1017a3
10 conflicts on slot
0xebc0f21b88…6e5a23
Audit this contract →
← previous block
·
next block →
recent activity